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

["Camille Fournier (JIRA)" <ji...@apache.org>]

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

Camille Fournier commented on ZOOKEEPER-2348:
---------------------------------------------

In the first scenario, you say that the session expired, and the removal happened, then fault, then it wasn't removed. Does the new leader eventually detect the session expiration, or does it never detect it?

In the second scenario, is the delete returned as succeeded to the client?

> 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: Chen Ningning
>
> 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.3.4#6332)