cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-520) Implement Range Repairs
Date Tue, 24 Nov 2009 21:42:39 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stu Hood updated CASSANDRA-520:
-------------------------------

    Attachment: 520-selective-1-decorated-keys-for-range-command.diff
                520-bulk-2-repair-strategy-by-fraction.diff
                520-bulk-1-use-streaming-api.diff

I've rebased these patches, and added selection of 'bulk' or 'selective' (range command) style
repair. They are completely disjoint, and should probably be merged separately: '520-bulk'
depends on the latest patchset from #193, but '520-selective' applies to trunk.

I think 520-bulk is ready for merge, and since repair will still be a manual process in 0.5,
requiring an anti-compaction for repair seems reasonable.

> 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-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.


Mime
View raw message