You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/06/01 03:47:04 UTC

[jira] [Resolved] (ZOOKEEPER-2797) Invalid TTL from misbehaving client nukes zookeeper

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han resolved ZOOKEEPER-2797.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.5.4
                   3.6.0

Issue resolved by pull request 267
[https://github.com/apache/zookeeper/pull/267]

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