cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <>
Subject [jira] [Comment Edited] (CASSANDRA-5062) Support CAS
Date Mon, 25 Feb 2013 06:00:17 GMT


Piotr Kołaczkowski edited comment on CASSANDRA-5062 at 2/25/13 5:58 AM:

+1 for Paxos.

I particularly like the idea it doesn't rely on having one distinguished coordinator (proposer)
to guarantee correctness.
      was (Author: pkolaczk):
    +1 for Paxos.
> 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