You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/05/10 23:59:56 UTC

[jira] [Commented] (ZOOKEEPER-964) How to avoid dead nodes generated? These nodes can't be deleted because there parent don't have delete and setacl permission.

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

Michi Mutsuzaki commented on ZOOKEEPER-964:
-------------------------------------------

This is not really fixable with the current ZooKeeper ACLs because you can't give back admin privilege to yourself. I'll close this as wontfix unless somebody has an idea on how to fix this.

> How to avoid dead nodes generated? These nodes can't be deleted because there parent don't have delete and setacl permission.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-964
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-964
>             Project: ZooKeeper
>          Issue Type: Wish
>          Components: server
>    Affects Versions: 3.3.2
>         Environment: i686-suse-linux
>            Reporter: allengao
>             Fix For: 3.5.0
>
>         Attachments: AclTest4ZKGroup.cpp
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> When a node which do not have setacl and delete permission was created (eg. permits=0x01), its children will never be deleted, even use superDigest。So, how to avoid this situation?



--
This message was sent by Atlassian JIRA
(v6.2#6252)