cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2606) Expose through JMX the ability to repair only the primary range
Date Thu, 05 May 2011 11:10:03 GMT


Sylvain Lebresne commented on CASSANDRA-2606:

Wait a minute ... that doesn't really work :(

Or more precisely, repairing a given range on a node N only make sure that N has this range
up to date. The other replica for this range may not be fully up to date on that range. Meaning
that running repair on the primary range for all node won't result in a fully repaired ring.

Actually I think the right fix would be to make it so that repairing a range really repair
this range on all the replica for this range, independently of which node we connected to
to start the repair. I've created CASSANDRA-2610 for that. So sorry about that but I think
we should wait on that last ticket before committing this.

> Expose through JMX the ability to repair only the primary range
> ---------------------------------------------------------------
>                 Key: CASSANDRA-2606
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.8.0
>         Attachments: 0001-Add-JMX-commands-to-repair-primary-range-v2.patch, 0001-Add-JMX-commands-to-repair-primary-range.patch
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> CASSANDRA-2324 introduces the ability to do a repair only on a given range. This ticket
proposes to add a nodetool repairPrimaryRange to trigger the repair of only the primary range
of a node. This allows to repair a full cluster without any work duplication (or at least
make it much simpler). This also introdude a global_repair command to clustertool to trigger
the primary range repair on each node of the cluster one after another (we could do all in
parallel, but that's probably not nice on the cluster).

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message