You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Luís Ferreira (JIRA)" <ji...@apache.org> on 2011/06/22 16:58:47 UTC

[jira] [Commented] (CASSANDRA-2686) Distributed per row locks

    [ https://issues.apache.org/jira/browse/CASSANDRA-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053296#comment-13053296 ] 

Luís Ferreira commented on CASSANDRA-2686:
------------------------------------------

I've taken your advice and used Cages for the Read and Write locks. From this I constructed a Transaction system on top of Cassandra. As soon as I have some performance test results I'll put them here, as well as the code, if anyone is interested. 

It basically implements a write ahead log, taking advantage of the atomicity in per row updates, and of  idempotent updates. It also has a pre processing mechanism for transactions that do not know à priori the columns they will use (when using indexes, for example). 

> Distributed per row locks
> -------------------------
>
>                 Key: CASSANDRA-2686
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2686
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>         Environment: any
>            Reporter: Luís Ferreira
>              Labels: api-addition, features
>
> Instead of using a centralized locking strategy like cages with zookeeper, I would like to have it in a decentralized way. Even if it carries some limitations. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira