zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2169) Enable creation of nodes with TTLs
Date Wed, 04 May 2016 13:31:13 GMT

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

Jordan Zimmerman updated ZOOKEEPER-2169:
    Attachment: ZOOKEEPER-2169-3.patch

Fixed test failure

> Enable creation of nodes with TTLs
> ----------------------------------
>                 Key: ZOOKEEPER-2169
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2169
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: c client, java client, jute, server
>    Affects Versions: 3.6.0
>            Reporter: Camille Fournier
>            Assignee: Jordan Zimmerman
>             Fix For: 3.6.0
>         Attachments: ZOOKEEPER-2169-2.patch, ZOOKEEPER-2169-3.patch, ZOOKEEPER-2169.patch
> As a user, I would like to be able to create a node that is NOT tied to a session but
that WILL expire automatically if action is not taken by some client within a time window.
> I propose this to enable clients interacting with ZK via http or other "thin clients"
to create ephemeral-like nodes.
> Some ideas for the design, up for discussion:
> The node should support all normal ZK node operations including ACLs, sequential key
generation, etc, however, it should not support the ephemeral flag. The node will be created
with a TTL that is updated via a refresh operation. 
> The ZK quorum will watch this node similarly to the way that it watches for session liveness;
if the node is not refreshed within the TTL, it will expire.
> 1) Should we let the refresh operation set the TTL to a different base value?
> 2) If so, should the setting of the TTL to a new base value cause a watch to fire?
> 3) Do we want to allow these nodes to have children or prevent this similar to ephemeral

This message was sent by Atlassian JIRA

View raw message