[CASSANDRA-13704] Better handling of out of range tokens

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Legacy/Coordination, Legacy/Observability
• Severity: Normal
• Assignee: Unassigned
• Reporter: Sam Tunnicliffe
• Created: 20/Jul/17 15:34
• Updated: 16/Apr/19 09:30

Description

It is possible for nodes to have a divergent view of the ring, which can result in some operations being sent to the wrong nodes. This is an umbrella ticket to mitigate such issues by adding logging when a node is asked to perform an operation for tokens it does not own. This will be useful for detecting when the nodes' views of the ring diverge, which is not highly visible at the moment, and also for post-hoc analysis.

It may also be beneficial to straight up reject certain operations, though this will need to balance the risk of performing those ops against the consequences rejecting them has on availability.

Sub-Tasks

• Warn or error when receiving write requests for unowned token ranges: Open
• Warn or error when receiving a read request for unowned token ranges: Open
• Warn or error when receiving Merkle Tree requests for unowned token ranges: Open
• Warn or error when receiving stream requests or inbound streams that contain unowned token ranges: Open
• Warn or error when receiving hints for unowned token ranges: Open
• Add a nodetool command to display details of any tables containing unowned tokens: Open