[CASSANDRA-12311] Propagate TombstoneOverwhelmingException to the client

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.10
• Component/s: Legacy/Observability
• Labels: doc-impacting
• Impacts: Clients
• Assignee: Geoffrey Yu
• Reporter: Geoffrey Yu

Authors

Geoffrey Yu

Reviewers

Tom Hobbs

• Created: 26/Jul/16 23:57
• Updated: 06/Nov/19 21:58
• Resolved: 19/Aug/16 21:12

Description

Right now if a data node fails to perform a read because it ran into a TombstoneOverwhelmingException, it only responds back to the coordinator node with a generic failure. Under this scheme, the coordinator won't be able to know exactly why the request failed and subsequently the client only gets a generic ReadFailureException. It would be useful to inform the client that their read failed because we read too many tombstones. We should have the data nodes reply with a failure type so the coordinator can pass this information to the client.

Issue Links

• is related to: CASSANDRA-13342 Doc: Enumerate the possible values for <failurecode> in <reasonmap>