[
https://issues.apache.org/jira/browse/BOOKKEEPER-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686248#comment-13686248
]
Sijie Guo commented on BOOKKEEPER-619:
--------------------------------------
I don't think this would be an issue. when you formatted the metadata,
shouldn't you format the local bookie? it is supposed to the logic for a clear
consistence instance setup.
for example, if the /ledgers exists before, but the admin didn't run metadata
format, so there is no instance id in cookies file. but the bookie failed to
start due to other issues, the admin run metadata format again. the bookie
would still fail to start since the local bookie files are not consistent with
metadata format.
A consistent instance setup you should run local bookie format after metadata
format. This is what the format tools give you.
> Bookie should not create local cookie files if zookeeper is uninitialized
> -------------------------------------------------------------------------
>
> Key: BOOKKEEPER-619
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-619
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.2.1
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.2, 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-619-Bookie-should-not-create-local-cookie.patch
>
>
> If you download a distribution of bookkeeper-4.2.1 and try to start the
> bookie before initializing zookeeper, then the bookie will fail to start, but
> write the local cookie files with a null instance id. If you then initialize
> zookeeper with the "bin/bookkeeper shell metaformat", you will not be able to
> start the bookie as instance id of in zk will not match the null instance id
> in the bookie files.
--
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
