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

Posted to issues@zookeeper.apache.org by "Julia ida (Jira)" <ji...@apache.org> on 2022/04/05 03:39:00 UTC

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

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

Julia ida commented on ZOOKEEPER-2797:
--------------------------------------

h4. Description
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.

> 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
>            Priority: Major
>              Labels: ttl_nodes
>             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
(v8.20.1#820001)