[
https://issues.apache.org/jira/browse/ZOOKEEPER-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Wallez resolved ZOOKEEPER-3546.
---------------------------------------
Resolution: Not A Bug
I understand from the discussion that this is a feature rather than an unwanted
side effect of giving time for application to create childrens, and I won't
dispute that.
What led to reporting this is a problem we encountered when using Curator's
{{PersistentTtlNode}} that creates a container and adds a child to it, but
doesn't do it as a transaction.
So I'll address this issue in Curator.
> Containers that never have children stay forever
> ------------------------------------------------
>
> Key: ZOOKEEPER-3546
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3546
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.3, 3.5.5
> Reporter: Sylvain Wallez
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> {{ContainerManager}} does not delete containers whose cversion is zero to
> avoid situations where a container would be deleted before the application
> had the chance to create children.
> This caused issues in our application where the process stopped between
> container creation and child creation: the containers were never deleted.
> To avoid this while giving applications the time to create children, empty
> containers with a cversion of zero should be deleted after a grace period,
> e.g. not when they are first collected, but the second time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
