[jira] [Resolved] (CASSANDRA-5608) "Primary range" repair still isn't quite NTS-aware

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis resolved CASSANDRA-5608.
---------------------------------------

       Resolution: Invalid
    Fix Version/s:     (was: 1.2.6)
         Reviewer:   (was: yukim)
         Assignee:     (was: Jonathan Ellis)

The right way to use -pr is still to repair everywhere the data exists; if we made -pr affect everything in the DC regardless of other replicas, then repairing the full cluster would repair each range 1x for each DC, which is not what we want
                
> "Primary range" repair still isn't quite NTS-aware
> --------------------------------------------------
>
>                 Key: CASSANDRA-5608
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5608
>             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: http://www.atlassian.com/software/jira