Bug in WriteLock recipe implementation?
---------------------------------------
Key: ZOOKEEPER-645
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-645
Project: Zookeeper
Issue Type: Bug
Affects Versions: 3.2.2
Environment: 3.2.2 java 1.6.0_12
Reporter: Jaakko Laine
Priority: Minor
Not sure, but there seem to be two issues in the example WriteLock:
(1) ZNodeName is sorted according to session ID first, and then according to
znode sequence number. This might cause starvation as lower session IDs always
get priority. WriteLock is not thread-safe in the first place, so having
session ID involved in compare operation does not seem to make sense.
(2) if findPrefixInChildren finds previous ID, it should add dir in front of
the ID
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
