cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 翟玉勇 (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11409) set read repair chance to 0 but find read repair process in trace
Date Thu, 20 Apr 2017 07:57:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976268#comment-15976268
] 

翟玉勇 commented on CASSANDRA-11409:
---------------------------------

这个不是bug,
那个Read-repair DC_LOCAL是每次操作读取system_auth keyspace 的表时候dclocal_read_repair_chance
= 0.1时候触发的,只不过把读取权限表的trace信息显示上去了


> 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.15#6346)

Mime
View raw message