[
https://issues.apache.org/jira/browse/BOOKKEEPER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626199#comment-13626199
]
Sijie Guo commented on BOOKKEEPER-552:
--------------------------------------
{quote}
Doesn't the metadata command wipe out any old data? Do we provide a way to
migrate data or changing the number of slots is fixed and can't change once we
start an instance, unless once is willing to wipe out its data?
{quote}
yes. metadata format would wipe out all any old metadata.
actually, migration is complicated thing as we discussed last year. but as my
understanding, if we want to proceed migration, at least we need to guarantee
the target ledger metadata would generate ledger ids with source ledger manager
in same ledger id space. so actually ledger id is an independent and critical
metadata rather ledger metadata itself. so I would suggest the ledger format
should be fixed during the life cycle of an instance.
but NUM_SLOTS could not be changed only when we use NUM_SLOTS to partition
ledger metadata into different zookeeper ensembles. if this id generator is
used only in single ledger manager, it could be changed. [~jiannan] please
correct me if I made wrong understanding of this part.
{quote}
I don't mind doing it through your reconnectable zookeeper client, but then
this patch needs to be based on BOOKKEEPER-537, no?
{quote}
no, these two could be independent as Jiannan said.
> 64 Bits Ledger ID Generation
> ----------------------------
>
> Key: BOOKKEEPER-552
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-552
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server, hedwig-server
> Reporter: Jiannan Wang
> Assignee: Jiannan Wang
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-552.patch, BOOKKEEPER-552.patch,
> BOOKKEEPER-552.patch
>
>
> This task aims to find and implement 64 bits global unique ledger id
> generation mechanisms.
--
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
