[
https://issues.apache.org/jira/browse/CASSANDRA-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615076#comment-13615076
]
Staņislavs Koikovs commented on CASSANDRA-4775:
-----------------------------------------------
I think you could simplify counter implementation a little bit by creating 2
counters internally instead of 1 (increment counter and decrement counter). So
with RF=3 each counter replica would keep track of 6 sub-counters (2 local and
4 remote). To get counter value you sum all sub-counters and for conflict
resolution you take a sub-counter with higher value. I hope this makes sense.
> Counters 2.0
> ------------
>
> Key: CASSANDRA-4775
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4775
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Arya Goudarzi
> Labels: counters
> Fix For: 2.0
>
>
> The existing partitioned counters remain a source of frustration for most
> users almost two years after being introduced. The remaining problems are
> inherent in the design, not something that can be fixed given enough
> time/eyeballs.
> Ideally a solution would give us
> - similar performance
> - less special cases in the code
> - potential for a retry mechanism
--
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
