zookeeper-dev mailing list archives

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

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

Michael Han commented on ZOOKEEPER-2797:
----------------------------------------

Side note: I think it's good to have the ttl validation on server side anyway, but it would
also be good to have same validation on client side so invalid ttl value will be caught earlier
before sending over to server. I believe the Java client does ttl validation, so kazoo client
should do something similar.

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