cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12311) Propagate TombstoneOverwhelmingException to the client
Date Sat, 30 Jul 2016 04:57:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Geoffrey Yu updated CASSANDRA-12311:
------------------------------------
    Attachment: 12311-trunk-v2.txt

I've attached an updated patch that removes the new exception and instead adds a new {{reason}}
field within {{ReadFailureException}} that can be used to indicate why the read query failed.

> 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
>             Fix For: 4.x
>
>         Attachments: 12311-trunk-v2.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)

Mime
View raw message