[
https://issues.apache.org/jira/browse/ZOOKEEPER-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794925#comment-13794925
]
Hadoop QA commented on ZOOKEEPER-1783:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12608431/ZOOKEEPER-1783-ver7.patch
against trunk revision 1532152.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 new or modified 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 1.3.9)
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-Build/1697//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1697//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1697//console
This message is automatically generated.
> Distinguish initial configuration from first established configuration
> ----------------------------------------------------------------------
>
> Key: ZOOKEEPER-1783
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1783
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum, server
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1783.patch, ZOOKEEPER-1783-ver1.patch,
> ZOOKEEPER-1783-ver2.patch, ZOOKEEPER-1783-ver3.patch,
> ZOOKEEPER-1783-ver4.patch, ZOOKEEPER-1783-ver5.patch,
> ZOOKEEPER-1783-ver6.patch, ZOOKEEPER-1783-ver7.patch
>
>
> We need a way to distinguish an initial config of a server and an initial
> config of a running ensemble (before any reconfigs happen). Currently both
> have version 0.
> The version of a config increases with each reconfiguration, so the problem
> is just with the initial config.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
