[
https://issues.apache.org/jira/browse/BOOKKEEPER-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630092#comment-13630092
]
Ivan Kelly commented on BOOKKEEPER-438:
---------------------------------------
+1 to sijie's comment on migration. I don't think we should rely on the admin
running a tool though. We could add something to the LedgerLayout to specify
which ledger id generator is in use. If none specified, either use the current
implementation or upgrade using the information available in zk.
> Move ledger id generation out of LedgerManager
> ----------------------------------------------
>
> Key: BOOKKEEPER-438
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-438
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server, hedwig-server
> Reporter: Sijie Guo
> Assignee: Jiannan Wang
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-438.patch, BOOKKEEPER-438.patch,
> BOOKKEEPER-438.patch, BOOKKEEPER-438.patch, BOOKKEEPER-438.patch,
> BOOKKEEPER-438.patch, BOOKKEEPER-438.patch, BOOKKEEPER-438.patch
>
>
> Move id generation out of LedgerManager to ensure different ledger manager
> implementation shared same ledger id space in ZooKeeper, which is necessary
> for migration between different ledger managers.
--
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
