cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaakko Laine (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-704) Cluster-wide mutex (ZooKeeper integration)
Date Wed, 20 Jan 2010 00:54:54 GMT

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

Jaakko Laine commented on CASSANDRA-704:
----------------------------------------

Nobody is using it at the moment :) Just added #721 atomic increment/decrement operations,
which uses this. It is not suitable to expose this to clients, as it would make it very difficult
to avoid deadlocks. If clients need ZK for external locking, they can use it directly. This
is just for internal operations.

This can be put to contrib as well. Just placed it in service because thougth of it as "locking
service for the whole server".


> Cluster-wide mutex (ZooKeeper integration)
> ------------------------------------------
>
>                 Key: CASSANDRA-704
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-704
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jaakko Laine
>            Assignee: Jaakko Laine
>         Attachments: 704-cluster-mutex.patch, zookeeper-3.2.2.jar
>
>
> Provide a cluster-wide mutex (zookeeper integration). Not strictly needed at the moment,
but since it's done now, I'll post it here for community to review & decide if it should
be included. This would allow us to have atomic increment/decrement operations before vector
clocks, and might come handy in automatic load balancing and other future tasks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message