cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1090) make it possible to tell when repair has finished
Date Tue, 25 May 2010 12:57:30 GMT

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

Hudson commented on CASSANDRA-1090:
-----------------------------------

Integrated in Cassandra #445 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/445/])
    Add repair and move requests into AntiEntropyService.  patch by Stu Hood; reviewed by
jbellis for CASSANDRA-1090


> make it possible to tell when repair has finished
> -------------------------------------------------
>
>                 Key: CASSANDRA-1090
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1090
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Stu Hood
>             Fix For: 0.6.2, 0.7
>
>         Attachments: 0001-Add-repair-sessions-and-move-requests-into-AntiEntro.patch,
0002-Don-t-trigger-repairs-when-rf-1.patch
>
>
> Stu said in IRC,
> "forceTableRepair sends TreeRequests everywhere, but doesn't wait for responses and repairs
to actually happen.  so you'd need to record which neighbors had responded for which cfs."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message