zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2348) Data between leader and followers are not synchronized.
Date Tue, 13 Jun 2017 22:06:00 GMT

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

Michael Han commented on ZOOKEEPER-2348:
----------------------------------------

This case might be the same as ZOOKEEPER-2355, and it could be a different case. Session expire
on cluster level requires quorum consensus, and if only (old) leader saw the session expired
but rest of the quorum does not, then after leader re-election the old leader should truncate
its log entry that records appertains to the session expire / ephemeral clean up, and reload
data base - and ephemeral node should reappear on old leader node. This is expected behavior
- that one node may be back in history. Other than this, the rest should be covered by ZOOKEEPER-2355.

> 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
>
> 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
(v6.4.14#64029)

Mime
View raw message