[
https://issues.apache.org/jira/browse/ZOOKEEPER-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt resolved ZOOKEEPER-2931.
-------------------------------------
Resolution: Fixed
Fix Version/s: 3.5.4
3.6.0
3.4.12
Issue resolved by pull request 413
[https://github.com/apache/zookeeper/pull/413]
> WriteLock recipe: incorrect znode ordering when the sessionId is part of the
> znode name
> ---------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2931
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2931
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.4.10, 3.5.3
> Reporter: Javier Cacheiro
> Fix For: 3.4.12, 3.6.0, 3.5.4
>
>
> When the nodes are sorted in WriteLock.java using a TreeSet the whole znode
> path is taken into account and not just the sequence number.
> This causes an issue when the sessionId is included in the znode path because
> a znode with a lower sessionId will appear as lower than other znode with a
> higher sessionId even if its sequence number is bigger.
> In specific situations this ended with two clients holding the lock at the
> same time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
