[ZOOKEEPER-1667] Watch event isn't handled correctly when a client reestablish to a server

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.3.6, 3.4.5
• Fix Version/s: 3.4.6, 3.5.0
• Component/s: server
• Assignee: Flavio Paiva Junqueira
• Reporter: Jacky007
• Created: 14/Mar/13 08:56
• Updated: 12/May/15 05:37
• Resolved: 22/Oct/13 10:56

Description

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.

Issue Links

• relates to: ZOOKEEPER-2182 Several test suites are not running during pre-commit, because their names do not end with "Test".