[CASSANDRA-11409] set read repair chance to 0 but find read repair process in trace

• Type: Bug
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Component/s: Legacy/CQL, Legacy/Distributed Metadata
• Labels: lhf

Environment

Cassandra 2.1.13 with centos 7

• Severity: Low
• Complexity: Low Hanging Fruit
• Assignee: Unassigned
• Reporter: Ryan Cho
• Created: 23/Mar/16 06:19
• Updated: 13/Jun/19 18:28

Description

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