Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Sun, 6 Aug 2017 03:36:02 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.13092604.1501880016000.101058.1501990562364@Atlassian.JIRA>
In-Reply-To: <JIRA.13092604.1501880016000@Atlassian.JIRA>
References: <JIRA.13092604.1501880016000@Atlassian.JIRA> <JIRA.13092604.1501880016609@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-2865) Reconfig Causes Inconsistent
 Configuration file among the nodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 06 Aug 2017 03:36:09 -0000


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2865?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
16115605#comment-16115605 ]=20

ASF GitHub Bot commented on ZOOKEEPER-2865:
-------------------------------------------

GitHub user shralex opened a pull request:

    https://github.com/apache/zookeeper/pull/328

    ZOOKEEPER-2865: Reconfig Causes Inconsistent Configuration file among=
=E2=80=A6

    =E2=80=A6 the nodes

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shralex/zookeeper ZOOKEEPER-2865

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/328.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #328
   =20
----
commit 4d428e520f5a00f8311bc4618d45f9da5b9e26c1
Author: Alexander Shraer <ashraer@apple.com>
Date:   2017-08-06T03:34:48Z

    ZOOKEEPER-2865: Reconfig Causes Inconsistent Configuration file among t=
he nodes

----


> Reconfig Causes Inconsistent Configuration file among the nodes
> ---------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2865
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2865
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection, quorum, server
>    Affects Versions: 3.5.3
>            Reporter: Jeffrey F. Lukman
>         Attachments: ZK-2865.pdf
>
>
> When we run our Distributed system Model Checking (DMCK) in ZooKeeper v3.=
5.3
> by following the workload in ZK-2778:
> - initially start 2 ZooKeeper nodes
> - start 3 new nodes
> - do a reconfiguration (the complete reconfiguration is attached in the d=
ocument)
> We think our DMCK found this following bug:
> - while one of the just joined nodes has not received the latest configur=
ation update=20
> (called as node X), the initial leader node closed its port,=20
> therefore causing the node X to be isolated.
> For complete information of the bug, please see the document that is atta=
ched.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)