[
https://issues.apache.org/jira/browse/BOOKKEEPER-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063922#comment-15063922
]
Enrico Olivelli commented on BOOKKEEPER-878:
--------------------------------------------
if it is possible we would like to preserve existing ledgers, but if it is not
possible we can make otherway.
actually I tested that even dropping all the ledgers it is not possibile to
switch because the Bookie does not boot if I change the LedgerManagerFactory
we are using bookkeeper for many purposes, for instance:
- state replication (using followers that tail active ledgers): so readers are
on different JVMS, but readers can be stopped for some time
- a write-ahead-log: reads are done only for recovery/replay of transactions,
readers are new JVMs which are spawned for recovery
use wrote "This requires a bit code change to allow HierarchicalLedgerManager
to read ledgers that were already created by FlatLedgerManager.", so a new
implementation and release (probabily 4.3.3) is needed ?
thank you
> verify switching FlatLedgerManager to HierarchicalLedgerManager
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-878
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-878
> Project: Bookkeeper
> Issue Type: Task
> Reporter: Sijie Guo
> Assignee: Sijie Guo
>
> after BOOKKEEPER-438 is in, it is possible to switch FlatLedgerManager to
> HierarchicalLedgerManager.
> - we need to verify whether it works
> - add test cases to cover these steps
> - documentation about the steps
> if this is verified, port BOOKKEEPER-438 back to 4.3.* branch to make it
> available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
