You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/01/14 19:52:46 UTC

[jira] Issue Comment Edited: (CASSANDRA-1985) read repair on CL.ONE regression

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

Jonathan Ellis edited comment on CASSANDRA-1985 at 1/14/11 1:51 PM:
--------------------------------------------------------------------

The "second RR" (that is, the second read request, for performing repair when a mismatch was detected by the digest read) is this one:

{code}
                RepairCallback<Row> handler = repair(command, endpoints);
...
                repairResponseHandlers.add(handler);
...
            for (RepairCallback<Row> handler : repairResponseHandlers)
            {
                try
                {
                    Row row = handler.get();
{code}

      was (Author: jbellis):
    The second RR is this one:

{code}
                RepairCallback<Row> handler = repair(command, endpoints);
...
                repairResponseHandlers.add(handler);
...
            for (RepairCallback<Row> handler : repairResponseHandlers)
            {
                try
                {
                    Row row = handler.get();
{code}
  
> 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.