[
https://issues.apache.org/jira/browse/CASSANDRA-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278432#comment-16278432
]
Hong Pai commented on CASSANDRA-11409:
--------------------------------------
As [~cam1982] said, I found it too.
I use TWCS and set the dclocal_read_repair_chance / read_repair_chance to 0.0
for a table.
But after I restart my C* nodes on by one without manual nodetool repair , and
new write and read request come in... I found SSTable overlapping.
I think the only reason is read repair.
See https://issues.apache.org/jira/browse/CASSANDRA-13910
> 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
> Priority: Minor
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
