[
https://issues.apache.org/jira/browse/ZOOKEEPER-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030677#comment-16030677
]
Hadoop QA commented on ZOOKEEPER-2797:
--------------------------------------
+1 overall. GitHub Pull Request Build
+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 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/753//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/753//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/753//console
This message is automatically generated.
> Invalid TTL from misbehaving client nukes zookeeper
> ---------------------------------------------------
>
> Key: ZOOKEEPER-2797
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2797
> Project: ZooKeeper
> Issue Type: Bug
> Components: security, server
> Affects Versions: 3.6.0
> Reporter: Patrick White
>
> I was adding container and TTL support to kazoo, and managed to screw
> something up which set the TTL to a negative value. This invalid TTL blew up
> the commit processor, and got written to the log, preventing the zookeepers
> from starting back up.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
