Details
Description
ZooKeeper ephemeral node is never deleted if follower fail while reading the proposal packet
The scenario is as follows:
- Configure three node ZooKeeper cluster, lets say nodes are A, B and C, start all, assume A is leader, B and C are follower
- Connect to any of the server and create ephemeral node /e1
- Close the session, ephemeral node /e1 will go for deletion
- While receiving delete proposal make Follower B to fail with SocketTimeoutException. This we need to do to reproduce the scenario otherwise in production environment it happens because of network fault.
- Remove the fault, just check that faulted Follower is now connected with quorum
- Connect to any of the server, create the same ephemeral node /e1, created is success.
- Close the session, ephemeral node /e1 will go for deletion
- /e1 is not deleted from the faulted Follower B, It should have been deleted as it was again created with another session
- /e1 is deleted from Leader A and other Follower C
Attachments
Attachments
Issue Links
- causes
-
ZOOKEEPER-3040 flaky test EphemeralNodeDeletionTest
- Resolved
- is related to
-
KNOX-1599 Upgrade zookeeper to 3.4.13 and curator-test to 2.13.0
- Closed
-
ZOOKEEPER-2348 Data between leader and followers are not synchronized.
- Open
-
CURATOR-409 TestingQuorumPeerMain does not work with Zookeeper 3.5.3-beta
- Resolved
- links to
(1 links to)
1.
|
ZOOKEEPER-2355 fix for branch-3.4 | Resolved | Unassigned |