[
https://issues.apache.org/jira/browse/CASSANDRA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590705#comment-13590705
]
Cristian Opris commented on CASSANDRA-5062:
-------------------------------------------
There is this paper that might be of interest, Consensus on Transaction Commit:
http://research.microsoft.com/apps/pubs/default.aspx?id=64636
I haven't yet studied it in detail but may give some ideas.
"Paxos made live" seems centered on the idea of having a replicated log. Not
sure this applies to what we want to do. There are details on how to do that
however in the papers cited, the more relevant I think:
Lampson, B. W. How to build a highly available system using consensus.
Schneider, F. B. Implementing fault-tolerant services using the state machine
approach: A tutorial.
Google has links to the papers
> 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
