cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5062) Support CAS
Date Wed, 27 Feb 2013 05:18:14 GMT


Jonathan Ellis commented on CASSANDRA-5062:

bq. The thing that is stopping me from hacking together a Paxos prototype is, where do we
store the accepted-but-not-committed proposals?

Thinking that just dumping them to a separate file (like the pre-2.0 manifest) will be adequate
to start with.  We can also trade off how fine-grained the paxos ensemble is (one per row,
vs one per vnode) for storage space.
> Support CAS
> -----------
>                 Key: CASSANDRA-5062
>                 URL:
>             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:

View raw message