You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Jeffrey F. Lukman (JIRA)" <ji...@apache.org> on 2017/07/24 20:37:00 UTC
[jira] [Created] (ZOOKEEPER-2855) Rebooting a Joined Node Failed
Due The Joined Node Previously Failed to Update Its Configuration Correctly
Jeffrey F. Lukman created ZOOKEEPER-2855:
--------------------------------------------
Summary: Rebooting a Joined Node Failed Due The Joined Node Previously Failed to Update Its Configuration Correctly
Key: ZOOKEEPER-2855
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2855
Project: ZooKeeper
Issue Type: Bug
Components: leaderElection, quorum, server
Affects Versions: 3.5.3
Reporter: Jeffrey F. Lukman
We are testing our distributed system model checking (DMCK)
by directing our DMCK to reproduce the ZooKepeer-2172 bug in the ZooKeeper v3.5.3.
After some explloration, our DMCK found that the ZooKeeper-2172 still linger in the reported fixed version, ZooKeeper v.3.5.3.
Here we attached the complete bug scenario to reproduce the bug.
We have communicated this bug to [~shralex] and he has confirmed that this bug exists
and he has found a fix for this bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)