[
https://issues.apache.org/jira/browse/ZOOKEEPER-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Stuardo updated ZOOKEEPER-2888:
-------------------------------------
Summary: Reconfig Command Isolates One of the Nodes when all ports change
(was: Reconfig Causes Inconsistent Configuration file among the nodes)
> Reconfig Command Isolates One of the Nodes when all ports change
> ----------------------------------------------------------------
>
> Key: ZOOKEEPER-2888
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2888
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.5.3
> Reporter: Cesar Stuardo
> Attachments: ZK-2888.pdf
>
>
> When we run our Distributed system Model Checking (DMCK) in ZooKeeper v3.5.3
> by following the workload (complete details attached):
> 1. start a 5 node cluster (all nodes know each other).
> 2. wait for the cluster to reach a steady state.
> 3. issue reconfig command which does not add or remove nodes but changes all
> the ports of the existing cluster (no role change either).
> We observer that in some situations, one of the followers my end up isolated
> since the other nodes change their ports and end up setting up new
> connections. The consequence is similar to the one at
> [ZK-2865|https://issues.apache.org/jira/browse/ZOOKEEPER-2865?jql=] but the
> scenario is different.
> We provide further details in the attached document.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
