[
https://issues.apache.org/jira/browse/ZOOKEEPER-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528906#comment-15528906
]
ASF GitHub Bot commented on ZOOKEEPER-2169:
-------------------------------------------
GitHub user Randgalt opened a pull request:
https://github.com/apache/zookeeper/pull/82
[ZOOKEEPER-2169] Enable creation of nodes with TTLs
This patch takes advantage of 3.5's container support. Most of the work
needed to support TTLs is there already.
In order not to break on-disk and protocol compatibility the ephemeralOwner
is yet-again overloaded to have special meaning.
New opcodes and transaction records had to be added in a similar manner to
Containers
NOTE: This patch was originally in Review Board and was moved to Github for
ease/convenience. RB link:
https://reviews.apache.org/r/46983/#comment214810
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Randgalt/zookeeper ZOOKEEPER-2169
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/82.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #82
----
commit 9cb973c7ff77b9a12c2fb74d05da38b79ab34c07
Author: randgalt <[email protected]>
Date: 2016-09-28T08:32:50Z
This patch takes advantage of 3.5's container support. Most of the work
needed to support TTLs is there already.
In order not to break on-disk and protocol compatibility the ephemeralOwner
is yet-again overloaded to have special meaning.
New opcodes and transaction records had to be added in a similar manner to
Containers
NOTE: This patch was originally in Review Board and was moved to Github for
ease/convenience. RB link:
https://reviews.apache.org/r/46983/#comment214810
----
> 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-4.patch, ZOOKEEPER-2169-5.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.
> QUESTIONS:
> 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 nodes?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
