[
https://issues.apache.org/jira/browse/ZOOKEEPER-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968108#comment-13968108
]
Hadoop QA commented on ZOOKEEPER-1699:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12640025/ZOOKEEPER-1699-v3.patch
against trunk revision 1586200.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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 failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2043//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2043//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2043//console
This message is automatically generated.
> Leader should timeout and give up leadership when losing quorum of last
> proposed configuration
> ----------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1699
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1699
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Priority: Blocker
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1699-v1.patch, ZOOKEEPER-1699-v2.patch,
> ZOOKEEPER-1699-v3.patch, ZOOKEEPER-1699.patch
>
>
> A leader gives up leadership when losing a quorum of the current
> configuration.
> This doesn't take into account any proposed configuration. So, if
> a reconfig operation is in progress and a quorum of the new configuration is
> not
> responsive, the leader will just get stuck waiting for it to ACK the reconfig
> operation, and will never timeout.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
