Jonathan Ellis created CASSANDRA-5608: -----------------------------------------
Summary: "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 Assignee: Jonathan Ellis Fix For: 1.2.6 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 DC1, 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