[
https://issues.apache.org/jira/browse/CASSANDRA-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981846#action_12981846
]
Kelvin Kakugawa commented on CASSANDRA-1985:
--------------------------------------------
Yes, you're right, that does schedule it, once.
The process for CL.ONE is:
1) schedule RR for data+digest and watch for a DigestMismatchException,
2) catch DME and call repair() to do a RR for data-only.
However, the handler for the second RR (that repair() returns) is never used.
So, even though it's collecting all the data repair messages, the RRR's
resolve() never gets called.
> read repair on CL.ONE regression
> --------------------------------
>
> Key: CASSANDRA-1985
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1985
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0, 0.7.1, 0.8
> Reporter: Kelvin Kakugawa
> Assignee: Kelvin Kakugawa
> Fix For: 0.7.1, 0.8
>
> Attachments:
> CASSANDRA-1985-0001-fix-CL.ONE-read-repair-regression.patch
>
>
> read repair w/ CL.ONE had a regression.
> The RepairCallback was dropped (in the background for CL.ONE), so
> ReadResponseResolver : resolve() was never called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
