[
https://issues.apache.org/jira/browse/BOOKKEEPER-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063537#comment-15063537
]
Sijie Guo commented on BOOKKEEPER-878:
--------------------------------------
[~eolivelli] I looked at this ticket. It is possible to switch from
FlatLedgerManager to HierarchicalLedgerManager. But since the ledger path would
be a bit difference between FlatLedgerManager and HierarchicalLedgerManager.
This requires a bit code change to allow HierarchicalLedgerManager to read
ledgers that were already created by FlatLedgerManager.
and the upgrade flow would be:
- upgrade all the bookies code first so the bookies understand both ledgers
created by FlatLedgerManager and HierarhicalLedgerManager
- once all the bookies are upgraded, upgrade the reader who only read ledgers.
so all the readers could understand the ledgers created by FlatLedgerManager
and HierarchicalLedgerManager.
- upgrade writers' binary first (all the writers are still generating ledgers
in FlatLedgerManager format).
- once all the writers understand the path for both FlatLedgerManager and
HierarchicalLedgerManager, upgrade the configuration to generate ledgers by
HierarchicalLedgerManager.
does that make senses to you?
And couple questions?
- do you want to move the ledgers that created by FlatLedgerManager to the
HierarchicalLedgerManager?
- do you run writers separately from readers? or they are in same jvm process?
> 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)
