[
https://issues.apache.org/jira/browse/BOOKKEEPER-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398295#comment-13398295
]
Ivan Kelly commented on BOOKKEEPER-304:
---------------------------------------
Regarding the patch, BOOKKEEPER-203 changed the ledger managers so that
references to ZooKeeper were completely removed. This was done because for some
usecases, zookeeper isn't suitable for storing ledger metadata (like a cluster
with 1billion ledgers).
This patch should use the new LedgerManager. I can use asyncProcessLedgers to
get the list of ledger ids, and with each ID, use readLedgerMetadata to get the
ensembles.
Generating this map should be quite quick (of course we should verify this
statement) and given that bookie crashes should be rather rare, we can
regenerate each time a bookie goes down.
I don't think watchers is a good approach here, as you will end up with as many
watchers as you have ledgers, which could be millions, and in any case, when
the watcher is triggered you have get the whole ledger list again anyhow. Also,
watching is zk specific, so not possible through just the LedgerManager
interface.
> Prepare bookie vs ledgers cache and will be used by the Auditor
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-304
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-304
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-304.1.patch
>
>
> This JIRA discusses how to build bookie -> ledgers cache and this will be
> used by the Auditor to publish the suspected ledgers of failed bookies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
