[
https://issues.apache.org/jira/browse/ZOOKEEPER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan updated ZOOKEEPER-78:
------------------------------------
Attachment: writeLock_protocol_version3.patch
Here is an improved version.
* we use more optimal comparison by using a ZNodeName object which caches the
prefix & sequence number for ordering node names. We can also use this to order
node names using different prefixes - maybe useful for read/write locks
* fixed a bug and enhanced the test case so that we now test that a leader is
established; then when that leader fails another leader/owner is created
> added a high level protocol/feature - for easy Leader Election or exclusive
> Write Lock creation
> -----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-78
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-78
> Project: Zookeeper
> Issue Type: New Feature
> Components: java client
> Affects Versions: 3.0.0
> Reporter: james strachan
> Assignee: james strachan
> Attachments: writeLock_protocol_version3.patch
>
>
> Here's a patch which adds a little WriteLock helper class for performing
> leader elections or creating exclusive locks in some directory znode. Note
> its an early cut; am sure we can improve it over time. The aim is to avoid
> folks having to use the low level ZK stuff but provide a simpler high level
> abstraction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
