[
https://issues.apache.org/jira/browse/CASSANDRA-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096028#comment-13096028
]
Sylvain Lebresne commented on CASSANDRA-2606:
---------------------------------------------
bq. nit: should we call it the "partitioner range" or something else b/s
"primary," which has connotations that we'd prefer to avoid?
Agreed, I was thinking the same thing. Not sure 'partitioner range' is really
meaningful but I agree that it'll avoid confusion. I was also thinking of
'local range' as an alternative, but it's not really more meaningful, just
shorter.
> Expose through JMX the ability to repair only the primary range
> ---------------------------------------------------------------
>
> Key: CASSANDRA-2606
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2606
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: repair
> Fix For: 1.0
>
> Attachments: 0001-Add-JMX-commands-to-repair-primary-range-v2.patch,
> 0001-Add-JMX-commands-to-repair-primary-range-v3.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: http://www.atlassian.com/software/jira
