Re: Implementing locks using cassandra only

Sorry, another thought was when storing in the Number CF how about using the the number as the column name and the client ID as the column value. That way you could do a slice to get the highest number, and the client can still assemble the hash of client_id to number. AaronOn 14 Sep, 2010,at 10:46

Re: Implementing locks using cassandra only

Thanks for the post it looks really handy. I found this page to help my simple mind understand whats going on http://nob.cs.ucdavis.edu/classes/ecs150-1999-02/sync-bakery.html  I've got some thoughts / questions mostly about implementation...1. Any thoughts on how it would work with a dynamic numbe

Re: Implementing locks using cassandra only

Bakery algorithm is really interesting -- AFAIK it's the only mutex algorithm that doesn't assume an existing atomic operation like CAS. On Mon, Sep 13, 2010 at 11:46 AM, Thorsten von Eicken wrote: > I've been musing about how to implement locks using just cassandra, i.e. > without sql db or zook

Implementing locks using cassandra only

I've been musing about how to implement locks using just cassandra, i.e. without sql db or zookeeper. I wrote up what I've come up with on the wiki (it's a bit too long for an email) at . I'm wondering whether I've overlooked something, especially I'm n