cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2495) Add a proper retry mechanism for counters in case of failed request
Date Thu, 03 Nov 2011 15:25:32 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143236#comment-13143236
] 

T Jake Luciani commented on CASSANDRA-2495:
-------------------------------------------

CASSANDRA-2034 does improve this a bit, since we know a hint was stored for the timed out
replica(s).
                
> Add a proper retry mechanism for counters in case of failed request
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-2495
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2495
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: Sylvain Lebresne
>         Attachments: marker_idea.txt
>
>
> Contrarily to standard insert, counter increments are not idempotent. As such, replaying
a counter mutation when a TimeoutException occurs could lead to an over-count. This alone
limits the use cases for which counters are a viable solution, so we should try to come up
with a mechanism that allow the replay of a failed counter mutation without the risk of over-count.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message