[
https://issues.apache.org/jira/browse/CASSANDRA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531096#comment-13531096
]
Jonathan Ellis commented on CASSANDRA-5062:
-------------------------------------------
Possible solutions include
# External locking, e.g. via ZooKeeper as in Cages
(http://code.google.com/p/cages/)
# Native locking, e.g. the wait chain algorithm now implemented in Hector
(http://media.fightmymonster.com/Shared/docs/Wait%20Chain%20Algorithm.pdf)
# Leader election as in Spinnaker (http://arxiv.org/pdf/1103.2408.pdf)
> Support CAS
> -----------
>
> Key: CASSANDRA-5062
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5062
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Fix For: 2.0
>
>
> "Strong" consistency is not enough to prevent race conditions. The classic
> example is user account creation: we want to ensure usernames are unique, so
> we only want to signal account creation success if nobody else has created
> the account yet. But naive read-then-write allows clients to race and both
> think they have a green light to create.
--
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
