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 16:30:04 GMT

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

Michael Han commented on ZOOKEEPER-2797:

bq. the server should always be validating all fields of all requests.
Absolutely, to prevent bad clients. I mentioned client side check because if we control the
clients, then doing client side check is more efficient as it prevents unnecessary round trips.

bq. any insight into why create flags moved from being bitfield-like to an enum?
If you are referring to the EphemeralType as the enum, my guess would be for readability.

> 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

View raw message