[
https://issues.apache.org/jira/browse/ZOOKEEPER-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239736#comment-16239736
]
ASF GitHub Bot commented on ZOOKEEPER-2931:
-------------------------------------------
Github user javicacheiro commented on the issue:
https://github.com/apache/zookeeper/pull/413
Added unit tests and created JIRA issue:
https://issues.apache.org/jira/browse/ZOOKEEPER-2931
> 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
> Reporter: Javier Cacheiro
>
> 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)
