[
https://issues.apache.org/jira/browse/BOOKKEEPER-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632564#comment-13632564
]
Sijie Guo commented on BOOKKEEPER-562:
--------------------------------------
[~fpj]
I think we just need to respond more actively to the community's request. For
example this one, and also some other hbase guys requires some kind of
location-aware distribution schedules.
go back to this jira, there are two jiras related to their requirements:
BOOKKEEPER-562 and BOOKKEEPER-257. for listing ledgers, it would be handled in
BOOKKEEPER-257. for this issue, I am not sure what exactly they required. but I
think both LedgerHandle#isClosed and BookKeeper#isClosed(ledgerId) are useful.
I could add such call to avoid instantiate a LedgerHandle.
> Ability to tell if a ledger is closed or not
> --------------------------------------------
>
> Key: BOOKKEEPER-562
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-562
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Whitney Sorenson
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-562.patch
>
>
> We need to be able to differentiate between open and closed ledgers, because
> we want to persist ledgers which are closed and wait for ledgers that are
> open to close.
> There doesn't seem to be an easy way to get a list of closed / open ledgers
> or to query bk to ask if a specific ledger is open or closed.
--
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
