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 Wed, 27 Jul 2016 00:01:40 GMT


Geoffrey Yu updated CASSANDRA-12311:
    Fix Version/s: 4.x
           Status: Patch Available  (was: Open)

I've attached a proposed patch that implements these changes. It adds a new exception code
and also makes changes to internode messaging, so I've marked it for 4.x.

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