[
https://issues.apache.org/jira/browse/BOOKKEEPER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625704#comment-13625704
]
Sijie Guo commented on BOOKKEEPER-552:
--------------------------------------
{quote}
Writing to ZooKeeper seems to be a good way to guarantee agreement and to lock
the value, but I don't think we can change that value for an existing
deployment even if everyone agrees on the value because it will lead to an
incorrect mapping for ledgers created with the old value.
{quote}
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.
{quote}
you probably want to resubmit the getData operation in the case of a connection
loss event.
{quote}
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.
> 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
