cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-2783) Explore adding replay ID for counters
Date Mon, 25 Jul 2011 18:05:09 GMT

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

Sylvain Lebresne resolved CASSANDRA-2783.
-----------------------------------------

    Resolution: Duplicate

Closing this one as this is a duplicate of CASSANDRA-2495

> Explore adding replay ID for counters
> -------------------------------------
>
>                 Key: CASSANDRA-2783
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2783
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sylvain Lebresne
>
> If a counter write returns a TimeoutException, the client cannot retry its write without
risking an overcount.
> One idea to fix this would be to allow the client to specify a replay ID with each counter
write unique to the write. If the write timeout, the client would resubmit the write with
the same replay ID and the system would ensure that write is only replayed if the previous
write was not persisted.
> Of course, the last part of this ("the system would ensure ...") is the hard part. Still
worth exploring I believe.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message