[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-253:
-----------------------------------

    Attachment: ZOOKEEPER-253.patch

This patch updates the forrest doc to correctly discuss watch re-establishment 
during re-sync to a server in the cluster.

> documentation of DataWatcher state transition is misleading regarding auto 
> watch reset on reconnect
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-253
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-253
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.0.0, 3.0.1
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-253.patch
>
>
> the example code has
>            case SyncConnected:
>                // Everything is happy. Lets kick things off
>                // again by checking the existence of the znode
>                break;
> this is misleading - it should indicate that the watches are automatically 
> reset and therefor no call to exists is necessary
> also fix this in the same doc (looks like its old detail, no longer valid), 
> indicate that autoreset will happen on reconnect.
> If the client-side ZooKeeper libraries can reestablish the communication 
> channel to ZooKeeper, DataMonitor simply kicks everything off again with the 
> call to ZooKeeper.exists(). If it gets an event for a znode, it calls 
> ZooKeeper.exists() to find out what has changed. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to