[CASSANDRA-14722] New monotonic reads impl introduces risk during range movements

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Duplicate
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Legacy/Coordination
• Bug Category: Correctness - Transient Incorrect Response
• Severity: Critical
• Assignee: Unassigned Assign to me
• Reporter: Benedict Elliott Smith
• Created: 12/Sep/18 14:11
• Updated: 15/May/20 08:06
• Resolved: 17/Jul/19 11:13

Description

Previously on digest mismatch we upgraded to CL.ALL, which harmed availability.  However, because we do not have consistent range movements, when they are underway it is possible for both the coordinator of a query and one of its targets have stale ring information. 

In this case, we would previously have detected a digest mismatch and ensured ALL nodes responded before answering, so that any single stale node would have been detected.  In the new implementation, we try to get answers only from the nodes whose digests mismatched, so if the node were stale, it can respond with a stale data request also, reducing effective CL by one.

Issue Links

• duplicates: CASSANDRA-14740 BlockingReadRepair does not maintain monotonicity during range movements