zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1667) Watch event isn't handled correctly when a client reestablish to a server
Date Thu, 07 May 2015 18:35:01 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533155#comment-14533155
] 

Chris Nauroth commented on ZOOKEEPER-1667:
------------------------------------------

The test suite {{WatchEventWhenAutoReset}} that was introduced in this patch has not been
running during pre-commit, because the build's test inclusion pattern looks for classes ending
in "Test".  I filed a patch on ZOOKEEPER-2182 to rename it to {{WatchEventWhenAutoResetTest}}.

> Watch event isn't handled correctly when a client reestablish to a server
> -------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1667
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1667
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.3.6, 3.4.5
>            Reporter: Jacky007
>            Assignee: Flavio Junqueira
>            Priority: Blocker
>             Fix For: 3.4.6, 3.5.0
>
>         Attachments: ZOOKEEPER-1667-b3.4.patch, ZOOKEEPER-1667-b3.4.patch, ZOOKEEPER-1667-r34.patch,
ZOOKEEPER-1667-trunk.patch, ZOOKEEPER-1667.patch
>
>
> When a client reestablish to a server, it will send the watches which have not been triggered.
But the code in DataTree does not handle it correctly.
> It is obvious, we just do not notice it :)
> scenario:
> 1) Client a set a data watch on /d, then disconnect, client b delete /d and create it
again. When client a reestablish to zk, it will receive a NodeCreated rather than a NodeDataChanged.
> 2) Client a set a exists watch on /e(not exist), then disconnect, client b create /e.
When client a reestablish to zk, it will receive a NodeDataChanged rather than a NodeCreated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message