cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4723) Improve write timeout exceptions
Date Wed, 26 Sep 2012 17:19:07 GMT


Jonathan Ellis commented on CASSANDRA-4723:

shouldn't guaranteedAtomic be a constructor parameter, not get()?
> Improve write timeout exceptions 
> ---------------------------------
>                 Key: CASSANDRA-4723
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.0 beta 2
>         Attachments: 4723.txt
> Through the binary protocol (and to a lesser extend in thrift), we now expose more information
with a timeout, so that clients can take the right decision as far as retrying the operation
is concerned. Concerning write timeouts, there is two places where I think we should improve
that a bit:
> * regarding batchlog writes: what clients are interested in is to know if the option
was atomic basically. If it was, there is no good reason to retry the write, otherwise, you
should (or at least you know there might be inconsistencies if you don't).
> * we should return a separate exception for counter writes as in that case no retry should
ever be done.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message