[
https://issues.apache.org/jira/browse/CASSANDRA-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2495.
---------------------------------------
Resolution: Won't Fix
I don't think it can be done without a complete reworking of the counters
backend. And if that happens it will be a separate ticket, so closing this one.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
