[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Kakugawa updated CASSANDRA-1072:
---------------------------------------
Attachment: CASSANDRA-1072.112210.patch
re-based against trunk
material modifications:
- removed counter lock from 1546
- reverse order of read/write for commutative operations
- race condition: may potentially miss an MT, but never double counts (compare
normal: may reconcile an MT twice, but never misses)
note: the above is a more graceful race condition, than the normal code path.
however, it does make eventual consistency more eventual.
further note: if perfect accuracy is required, a more fine-grained lock
strategy should be implemented.
> Increment counters
> ------------------
>
> Key: CASSANDRA-1072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1072
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Johan Oskarsson
> Assignee: Kelvin Kakugawa
> Attachments: CASSANDRA-1072.112210.patch, CASSANDRA-1072.patch,
> increment_test.py, Partitionedcountersdesigndoc.pdf
>
>
> Break out the increment counters out of CASSANDRA-580. Classes are shared
> between the two features but without the plain version vector code the
> changeset becomes smaller and more manageable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
