You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2019/04/26 21:46:00 UTC

[jira] [Commented] (ZOOKEEPER-2348) Data between leader and followers are not synchronized.

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

Shawn Heisey commented on ZOOKEEPER-2348:
-----------------------------------------

Does this problem affect 3.4.x versions, or just 3.5.x?  A problem is being discussed on the solr-user mailing list and we're trying to figure out whether this bug could be involved.  The referenced version of Solr (7.7.1) includes ZK 3.4.13.

> Data between leader and followers are not synchronized.
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-2348
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2348
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.5.1
>            Reporter: Echo Chen
>            Priority: Major
>
> When client session expired, leader tried to remove it from session map and remove its EPHEMERAL znode, for example, /test_znode. This operation succeed on leader, but at the very same time, network fault happended and not synced to followers, a new leader election launched. After leader election finished, the new leader is not the old leader. we found the znode /test_znode still existed in the followers but not on leader
>  *Scenario :* 
> 1) Create znode E.g.  
> {{/rmstore/ZKRMStateRoot/RMAppRoot/application_1449644945944_0001/appattempt_1449644945944_0001_000001}}
> 2) Delete Znode. 
> 3) Network fault b/w follower and leader machines
> 4) leader election again and follower became leader.
> Now data is not synced with new leader..After this client is not able to same znode.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)