Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1393

ZooKeeper client exists() javadoc incorrectly states watcher(s) will be triggered on node deletion

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Invalid
    • Affects Version/s: 3.3.4, 3.4.2
    • Fix Version/s: None
    • Component/s: java client
    • Labels:
      None

      Description

      I found it very misleading that the javadoc for the exists() calls that take a boolean or a Watcher state that 'The watch will be triggered by a successful operation that creates/delete the node or sets the data on the node.'

      What I've seen from descriptions of bugs (older but this is this references it http://zookeeper-user.578899.n2.nabble.com/Exists-Watch-Triggered-by-Delete-td1490893.html) and my own personal usage is that watchers set on exists() are triggered when a non-existing node is now created or an existing node is changed. They are NOT triggered when the node already exists and is deleted.

      http://zookeeper.apache.org/doc/r3.4.3/api/index.html

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              maddogg14524 Gary Malouf
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 20m
                20m
                Remaining:
                Remaining Estimate - 20m
                20m
                Logged:
                Time Spent - Not Specified
                Not Specified