[
https://issues.apache.org/jira/browse/ZOOKEEPER-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shixiaoxiao updated ZOOKEEPER-4388:
-----------------------------------
Summary: Recover from network partition, follower/observer ephemerals nodes
is inconsistent with leader (was: ReadOnlyRequestProcessor doesn‘t filter
closeSession and createSession)
> Recover from network partition, follower/observer ephemerals nodes is
> inconsistent with leader
> ----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-4388
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4388
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.6.0, 3.6.3, 3.6.1, 3.6.2
> Environment: zk version 3.6.0 3.6.1 3.6.2
> the follower/observer network disconnection time exceeds session timeout
> Reporter: shixiaoxiao
> Priority: Major
> Labels: inconsistency, partitoned, zookeeper
> Fix For: 3.7
>
> Attachments: dataInconsistent.png
>
>
> The follower/observer enable read only. When the node returns to normal from
> the partitioned, the ephemerals nodes will be inconsistent with the leader
> node. The reason is that the request to close the timeout sessions is
> processed by the ReadOnly follower or observer when they are partitioned and
> the ephemerals nodes created by these sessions also are delete. When the
> leader node uses diff to synchronize data with the follower/observer node,
> the transaction that needs to be synchronized does not include the creation
> of temporary nodes which created by sessions closed by followers.So the
> follower/observer ephemerals nodes is inconsistent with leader.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
