[jira] [Created] (BOOKKEEPER-1096) When ledger is deleted, along with leaf node all the eligible branch nodes also should be deleted in ZooKeeper.

["Charan Reddy Guttapalem (JIRA)" <ji...@apache.org>]

Charan Reddy Guttapalem created BOOKKEEPER-1096:
---------------------------------------------------

             Summary: When ledger is deleted, along with leaf node all the eligible branch nodes also should be deleted in ZooKeeper.
                 Key: BOOKKEEPER-1096
                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1096
             Project: Bookkeeper
          Issue Type: Improvement
            Reporter: Charan Reddy Guttapalem
            Assignee: Charan Reddy Guttapalem


Currently when we delete a ledger, we delete just the leaf node in the ZK but we ignore about the branch nodes. This is ok for FlatLedgerManager, but for HierarchicalLedgerManagers, especially for LongHierarchicalLedgerManager, the number of internal nodes gets blown up over time and we would get into ZK capacity limitations. When ZK reaches the capacity limits, it will manifest in very severe performance and stability issues of cluster. So for HierarchicalLedgerManagers, when we delete a ledger we should optimistically recursively delete the parent znodes as well if they don’t have anymore child znodes. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)