[ZOOKEEPER-3546] Containers that never have children stay forever

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.3, 3.5.5
• Fix Version/s: 3.6.0
• Component/s: server
• Labels: pull-request-available
• Assignee: Jordan Zimmerman
• Reporter: Sylvain Wallez
• Created: 16/Sep/19 13:21
• Updated: 03/Dec/19 18:37
• Resolved: 25/Nov/19 14:38

Description

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.

Issue Links

• is related to: CURATOR-545 PersistentTtlNode can leave dangling containers behind
• links to: GitHub Pull Request #1091
• links to: GitHub Pull Request #1138
• links to: GitHub Pull Request #1158