zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2797) Invalid TTL from misbehaving client nukes zookeeper
Date Thu, 01 Jun 2017 04:39:04 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032435#comment-16032435
] 

Hudson commented on ZOOKEEPER-2797:
-----------------------------------

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #3410 (See [https://builds.apache.org/job/ZooKeeper-trunk/3410/])
ZOOKEEPER-2797: Defend against bad TTLs from misbehaving clients (hanm: rev 3824da0b649c6a6a698cfe6c79ca3d44a9e94f29)
* (edit) src/java/main/org/apache/zookeeper/server/PrepRequestProcessor.java
* (edit) src/java/test/org/apache/zookeeper/server/CreateTTLTest.java


> 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
>            Assignee: Patrick White
>             Fix For: 3.5.4, 3.6.0
>
>
> 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)

Mime
View raw message