[
https://issues.apache.org/jira/browse/ZOOKEEPER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849113#action_12849113
]
Flavio Paiva Junqueira commented on ZOOKEEPER-464:
--------------------------------------------------
This is great, Erwin! A few high-level comments:
# Could you summarize the changes of this patch? For example, it would be nice
to summarize how the garbage collector behaves with respect to removing entry
logs;
# The license text is missing in LedgerDeleteTest.java. That's why your patch
got a -1 in release audits;
# Could you detail the issue with BufferedChannel? Where is the problem
exactly? Why can't we fix it?
# We need documentation for these features. If we don't do it in this patch,
then we need to open another jira and make sure that the documentation makes it
to the same release as this patch. Right now it sounds like this feature will
go into 3.4.0.
> Need procedure to garbage collect ledgers
> -----------------------------------------
>
> Key: ZOOKEEPER-464
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-464
> Project: Zookeeper
> Issue Type: New Feature
> Components: contrib-bookkeeper
> Reporter: Flavio Paiva Junqueira
> Assignee: Erwin Tam
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-464.patch
>
>
> An application using BookKeeper is likely to use a large number of ledgers
> over time. Such an application might not need all ledgers created over time
> and might want to delete some of these ledgers to free up some space on
> bookies. The idea of this jira is to implement a procedure that enables an
> application to garbage-collect unwanted ledgers.
> To garbage-collect a ledger, we need to delete the ledger metadata on
> ZooKeeper, and delete the ledger data on corresponding bookies.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
