cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-6491) Timeout can send confusing information as to what their cause is
Date Mon, 16 Dec 2013 11:37:06 GMT


Sylvain Lebresne updated CASSANDRA-6491:

    Attachment: 6491.txt

> Timeout can send confusing information as to what their cause is
> ----------------------------------------------------------------
>                 Key: CASSANDRA-6491
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>             Fix For: 1.2.14
>         Attachments: 6491.txt
> We can race between the time we "detect" a timeout and the time we build the actual exception,
so that it's possible to have a timeout exception that pretends enough replica have actually
acknowledged the operation, which is thus slightly confusing to the user as to why it got
a timeout.
> That kind of race is rather unlikely in a healthy environment, but
shows that it's at least possible to trigger in a test environment.
> Note that it's definitively not worth synchronizing to avoid that that, but it could
maybe be simple enough to detect the race when building the exception and "correct" the ack
count. Attaching simple patch to show what I have in mind.
> Note that I don't entirely disagree that it's not "perfect", but as said above, proper
synchronization is just not worth it and it seems to me that it's not worth confusing users
over that.

This message was sent by Atlassian JIRA

View raw message