[
https://issues.apache.org/jira/browse/BOOKKEEPER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676428#comment-13676428
]
Flavio Junqueira commented on BOOKKEEPER-257:
---------------------------------------------
I found the problem. FlatLedgerManager#getLedgerRanges() has been fixed in
trunk due to the changes in ZOOKEEPER-596. The version of
FlatLedgerManager#getLedgerRanges() in the 4.2 branch does not work with one of
the tests in the b4.2 patch because the iterator initially returns that there
is an element even when there is no ledger. I'll see if I can port the changes
to getLedgerRanges().
> Ability to list all ledgers
> ---------------------------
>
> Key: BOOKKEEPER-257
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-257
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Ivan Kelly
> Assignee: Flavio Junqueira
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-257-b4.2.patch, BOOKKEEPER-257.patch,
> BOOKKEEPER-257.patch, BOOKKEEPER-257.patch, BOOKKEEPER-257.patch,
> BOOKKEEPER-257.patch
>
>
> When an application is using bookkeeper it must keep a copy of the ledger ids
> it creates so that they can be used later, and once they are no longer
> useful, deleted. However, in the case of a crash between ledger creation and
> persisting the application copy of the id, the ledger will be dangling.
> Therefore I propose we have the ability to get a list of all ledger ids,
> which clients can use for garbage collection. However, I don't think it
> should be part of the BookKeeper class, rather part of a new BookKeeperAdmin
> class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
