[
https://issues.apache.org/jira/browse/ZOOKEEPER-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555842#comment-15555842
]
Hadoop QA commented on ZOOKEEPER-2169:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12832146/ZOOKEEPER-2169-7.patch
against trunk revision 8d0154bcc21e58b6166eb5e360f72ce37699e072.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3469//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3469//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3469//console
This message is automatically generated.
> 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-6.patch,
> ZOOKEEPER-2169-7.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)
