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

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Invalid
• Component/s: Legacy/Tools
• Severity: Normal
• Assignee: Unassigned
• Reporter: Jonathan Ellis
• Created: 03/Jun/13 16:06
• Updated: 16/Apr/19 09:32
• Resolved: 03/Jun/13 16:12

Description

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.

Issue Links

• relates to: CASSANDRA-7317 Repair range validation is too strict