cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5608) "Primary range" repair still isn't quite NTS-aware
Date Thu, 20 Jun 2013 21:57:22 GMT


Jonathan Ellis commented on CASSANDRA-5608:

That was fixed in 1.2.5. CASSANDRA-5424
> "Primary range" repair still isn't quite NTS-aware
> --------------------------------------------------
>                 Key: CASSANDRA-5608
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2.5
>            Reporter: Jonathan Ellis
> Consider the case of a four node cluster, with nodes A and C in DC1, and nodes B and
D in DC2.  TokenMetadata will break this into ranges of (A-B], (B-C], (C-D], (D-A].
> If we have a single copy of a keyspace stored in DC1 only (none in DC2), then the current
code correctly calculates that node A is responsible for ranges (C-D], (D-A].
> But, if we add a copy in DC2, then we only calculate (D-A] as primary range.  This is
a bug; we should not care what copies are in other datacenters, when computing what to repair
in the local one.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message