[
https://issues.apache.org/jira/browse/CASSANDRA-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801847#action_12801847
]
Jonathan Ellis commented on CASSANDRA-704:
------------------------------------------
Who is calling CM.lock()? If it's intended to be exposed to thrift I don't see
that here, but I don't see any other uses either.
Is there a compelling reason to put this in core instead of contrib/?
> 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.
