zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norbert Kalmar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-723) ephemeral parent znodes
Date Tue, 19 Mar 2019 13:15:01 GMT

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

Norbert Kalmar commented on ZOOKEEPER-723:
------------------------------------------

This functionality is implemented by Container nodes: ZOOKEEPER-2163 (version 3.5.1+)
I'm closing this issue.

> ephemeral parent znodes
> -----------------------
>
>                 Key: ZOOKEEPER-723
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-723
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Benjamin Reed
>            Assignee: Daniel Gómez Ferro
>            Priority: Major
>              Labels: container_znode_type
>         Attachments: ZOOKEEPER-723.patch, ZOOKEEPER-723.patch
>
>
> ephemeral znodes have the nice property of automatically cleaning up after themselves
when the creator goes away, but since they can't have children it is hard to build subtrees
that will cleanup after the clients that are using them are gone.
> rather than changing the semantics of ephemeral nodes, i propose ephemeral parents: znodes
that disappear when they have no more children. this cleanup would happen automatically when
the last child is removed. an ephemeral parent is not tied to any particular session, so even
if the creator goes away, the ephemeral parent will remain as long as there are children.
> the when an ephemeral parent is created it will have an initial child, so that it doesn't
get immediately removed. i think this child should be an ephemeral znode with a predefined
name, "firstChild".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message