[
https://issues.apache.org/jira/browse/ZOOKEEPER-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115611#comment-16115611
]
Hadoop QA commented on ZOOKEEPER-2865:
--------------------------------------
+1 overall. GitHub Pull Request Build
+1 @author. The patch does not contain any @author tags.
+0 tests included. The patch appears to be a documentation patch that
doesn't require tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/927//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/927//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/927//console
This message is automatically generated.
> Reconfig Causes Inconsistent Configuration file among the nodes
> ---------------------------------------------------------------
>
> Key: ZOOKEEPER-2865
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2865
> Project: ZooKeeper
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.5.3
> Reporter: Jeffrey F. Lukman
> Assignee: Alexander Shraer
> Priority: Trivial
> 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
> document)
> We think our DMCK found this following bug:
> - while one of the just joined nodes has not received the latest
> configuration update
> (called as node X), the initial leader node closed its port,
> therefore causing the node X to be isolated.
> For complete information of the bug, please see the document that is attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
