cassandra-commits mailing list archives

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

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

Sylvain Lebresne updated CASSANDRA-2606:
----------------------------------------

    Attachment: 0001-Add-JMX-commands-to-repair-primary-range-v2.patch

{quote}
I think I'd rather have it be an option to repair (--primary-range-only) than a new command.

-1 on doing anything more with clustertool than putting it out of its misery (CASSANDRA-2607).
{quote}

Fair enough, v2 does both of those thing.

bq. How does "primary range repair" work with NTS, where ranges are unique to each DC?

Not sure what you mean by "ranges are unique to each DC". Even with NTS, the
primary ranges are still computed over the one full ring (that rule them all).
So picking the primary range still has the property we are interested in here,
that is "if you repair the primary range of *all* the node of the full
cluster, then you will have repaired the full ring without doing any work
twice".

Now it is true that since with NTS you compute your token assignment
separately in each DC you may end up with some node having tiny primary range
(for instance if you have the same number of nodes in each DC and only offset
the tokens by 1 across DC). In which case the repair on those nodes will be
very quick. But I don't think this is a problem in any way (every host will
still do roughly the same amount of work overall).

However, maybe what you meant is that "repair is not optimized for multi-DC
settings". Which is a very good remark but is really a whole new problem. I'll
open a ticket for that.


> 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
>             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: http://www.atlassian.com/software/jira

Mime
View raw message