[
https://issues.apache.org/jira/browse/CASSANDRA-6887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013805#comment-14013805
]
Aleksey Yeschenko commented on CASSANDRA-6887:
----------------------------------------------
[~baldrick] LOCAL_* or not should not have any impact here, really - there is
no distinction in the codebase based on this. An async read repair will be
triggered once all the requests are received, and the data will be repaired.
That said, can you post more info on the affected table(s)?
1. The keyspace RF, in each DC
2. The configured read_repair_chance and local_read_repair_chance values for
the affected tables
3. speculative_retry setting for the affected tables
Thanks.
> LOCAL_ONE read repair only does local repair, in spite of global digest
> queries
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-6887
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6887
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Cassandra 2.0.6, x86-64 ubuntu precise
> Reporter: Duncan Sands
> Assignee: Aleksey Yeschenko
> Fix For: 2.0.9, 2.1.0
>
> Attachments: 6887-2.0.txt
>
>
> I have a cluster spanning two data centres. Almost all of the writing (and a
> lot of reading) is done in DC1. DC2 is used for running the occasional
> analytics query. Reads in both data centres use LOCAL_ONE. Read repair
> settings are set to the defaults on all column families.
> I had a long network outage between the data centres; it lasted longer than
> the hints window, so after it was over DC2 didn't have the latest
> information. Even after reading data many many times in DC2, the returned
> data was still out of date: read repair was not correcting it.
> I then investigated using cqlsh in DC2, with tracing on.
> What I saw was:
> - with consistency ONE, after about 10 read requests a digest request would
> be sent to many nodes (spanning both data centres), and the data in DC2 would
> be repaired.
> - with consistency LOCAL_ONE, after about 10 read requests a digest request
> would be sent to many nodes (spanning both data centres), but the data in DC2
> would not be repaired. This is in spite of digest requests being sent to
> DC1, as shown by the tracing.
> So it looks like digest requests are being sent to both data centres, but
> replies from outside the local data centre are ignored when using LOCAL_ONE.
> The same data is being queried all the time in DC1 with consistency
> LOCAL_ONE, but this didn't result in the data in DC2 being read repaired
> either. This is a slightly different case to what I described above: in that
> case the local node was out of date and the remote node had the latest data,
> while here it is the other way round.
> It could be argued that you don't want cross data centre read repair when
> using LOCAL_ONE. But then why bother sending cross data centre digest
> requests? And if only doing local read repair is how it is supposed to work
> then it would be good to document this somewhere.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
