[
https://issues.apache.org/jira/browse/ZOOKEEPER-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254531#comment-16254531
]
Hudson commented on ZOOKEEPER-2931:
-----------------------------------
FAILURE: Integrated in Jenkins build ZooKeeper-trunk #3612 (See
[https://builds.apache.org/job/ZooKeeper-trunk/3612/])
ZOOKEEPER-2931: WriteLock recipe: Fix bug in znode ordering when the (phunt:
rev f299303add79250ec2181f6c03b15e3754825284)
* (edit)
src/recipes/lock/test/org/apache/zookeeper/recipes/lock/ZNodeNameTest.java
* (edit)
src/recipes/lock/src/java/org/apache/zookeeper/recipes/lock/ZNodeName.java
> 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.5.4, 3.6.0, 3.4.12
>
>
> 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)
