[
https://issues.apache.org/jira/browse/ZOOKEEPER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Tam updated ZOOKEEPER-464:
--------------------------------
Attachment: ZOOKEEPER-464.patch
Updated patch with documentation changes and fix so the unit tests for ledger
deletes won't error out intermittently. The problem was a bug in the
EntryLogger where the "BKLO" ByteBuffer header that is prepended to each entry
log was defined as a static object. If multiple Bookies within the JVM are
running, a race condition can occur if they are rolling over entry logs and
accessing this header at the same time. The end result is, some entry logs are
created without the header and that screws the entry log ledger extraction.
All new methods should have proper javadoc comments before them now too.
> 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-log.txt, ZOOKEEPER-464.patch,
> ZOOKEEPER-464.patch, 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.
