[ https://issues.apache.org/jira/browse/CASSANDRA-12311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tyler Hobbs updated CASSANDRA-12311: ------------------------------------ Resolution: Fixed Fix Version/s: (was: 4.x) 3.10 Status: Resolved (was: Awaiting Feedback) Okay, finally got a good dtest run. Everything looks good, so +1. Committed as {{39df31a06a35b221f55f17ed20947a1a2e33ee1a}} to trunk. I've opened a [dtest pull request|https://github.com/riptano/cassandra-dtest/pull/1263] for your changes there, which should be merged soon. Thanks [~geoffxy]! > Propagate TombstoneOverwhelmingException to the client > ------------------------------------------------------ > > Key: CASSANDRA-12311 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12311 > Project: Cassandra > Issue Type: Improvement > Reporter: Geoffrey Yu > Assignee: Geoffrey Yu > Priority: Minor > Labels: client-impacting, doc-impacting > Fix For: 3.10 > > Attachments: 12311-dtest.txt, 12311-trunk-v2.txt, 12311-trunk-v3.txt, > 12311-trunk-v4.txt, 12311-trunk-v5.txt, 12311-trunk.txt > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)