You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2016/03/30 16:27:25 UTC
[jira] [Updated] (CASSANDRA-11409) set read repair chance to 0 but
find read repair process in trace
[ https://issues.apache.org/jira/browse/CASSANDRA-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-11409:
-----------------------------------------
Labels: lhf (was: )
> set read repair chance to 0 but find read repair process in trace
> -----------------------------------------------------------------
>
> Key: CASSANDRA-11409
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11409
> Project: Cassandra
> Issue Type: Bug
> Components: CQL, Distributed Metadata
> Environment: Cassandra 2.1.13 with centos 7
> Reporter: Ryan Cho
> Labels: lhf
> Attachments: 螢幕快照 2016-03-23 下午2.06.10.png
>
>
> I have set dclocal_read_repair_chance and read_repair_chance to 0.0 for one month, but I still find "Read-repair DC_LOCAL" and "Initiating read-repair" activities in system_trace.events, and query was executed in these two days and long time after set read repair chance to 0.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)