[
https://issues.apache.org/jira/browse/BOOKKEEPER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625771#comment-13625771
]
Flavio Junqueira commented on BOOKKEEPER-552:
---------------------------------------------
bq. yes. so I think we should only write the NUM_SLOTS into zookeeper when
using bin/bookkeeper metaformat. using a lifecycle of an bookkeeper instance,
we shouldn't change the value until formatting next instance.
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? It is possibly
not a big deal.
bq. I think this could be addressed in a common place, using the reconnectable
zookeeper client in BOOKKEEPER-537, rather than being handled every place
processing the return code.
I don't mind doing it through your reconnectable zookeeper client, but then
this patch needs to be based on BOOKKEEPER-537, no?
> 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
