You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/06/06 18:55:21 UTC
[jira] [Updated] (BOOKKEEPER-619) Bookie should not create local
cookie files if zookeeper is uninitialized
[ https://issues.apache.org/jira/browse/BOOKKEEPER-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Kelly updated BOOKKEEPER-619:
----------------------------------
Attachment: 0001-BOOKKEEPER-619-Bookie-should-not-create-local-cookie.patch
> 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.3.0, 4.2.2
>
> 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