[
https://issues.apache.org/jira/browse/BOOKKEEPER-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690452#comment-13690452
]
Ivan Kelly commented on BOOKKEEPER-619:
---------------------------------------
{quote}but the existence of ledgerRootPath doesn't mean the metadata is
formatted{quote}
It may do. If you initialized your cluster with a bookkeeper version before we
added metaformat, then ledgerRootPath existence effectively meant that metadata
was formatted. If we weren't maintaining this behaviour then we could refuse to
write anything on the bookie if instanceid was null. We are maintaining it
though :/
I'll push in the patch. Thanks for reviewing.
> 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
