You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2009/12/05 03:29:20 UTC
[jira] Updated: (CASSANDRA-520) Implement Range Repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-520:
-------------------------------
Attachment: 520-bulk-2-repair-strategy-by-fraction.diff
520-bulk-1-use-streaming-api.diff
Rebased 520-bulk to apply on top of the latest edition of 193.
> Implement Range Repairs
> -----------------------
>
> Key: CASSANDRA-520
> URL: https://issues.apache.org/jira/browse/CASSANDRA-520
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Stu Hood
> Assignee: Stu Hood
> Fix For: 0.5
>
> Attachments: 520-bulk-1-use-streaming-api.diff, 520-bulk-1-use-streaming-api.diff, 520-bulk-2-repair-strategy-by-fraction.diff, 520-bulk-2-repair-strategy-by-fraction.diff, 520-selective-1-decorated-keys-for-range-command.diff
>
>
> After CASSANDRA-193, the TreeRequest/Response conversation will have generated a full list of Ranges that disagree between nodes. We need an operation that can efficiently batch repair the ranges, similar to what happens during read repair for a single key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.