cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Yu (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-12311) Propagate TombstoneOverwhelmingException to the client
Date Tue, 09 Aug 2016 00:19:20 GMT


Geoffrey Yu updated CASSANDRA-12311:
    Attachment: 12311-dtest.txt

Thanks for the help with the driver and the example test! I really appreciate it. :)

I've attached a patch meant to be applied on top of your {{CASSANDRA-12311-tests}} branch.
It modifies {{}} and
{{}} so that they check for the failure map when protocol v5 is used.
I also added another file, {{}} to test read failures due to reading
too many tombstones. I modeled it after {{}} and added tests for protocol
v3 and v4 as well.

> Propagate TombstoneOverwhelmingException to the client
> ------------------------------------------------------
>                 Key: CASSANDRA-12311
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Geoffrey Yu
>            Assignee: Geoffrey Yu
>            Priority: Minor
>              Labels: client-impacting, doc-impacting
>             Fix For: 4.x
>         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

View raw message