[
https://issues.apache.org/jira/browse/BOOKKEEPER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439429#comment-13439429
]
Sijie Guo commented on BOOKKEEPER-300:
--------------------------------------
{quote}
If cookie is of previous version, and Running Code is of version 4, then we
should support that cookie because of backward compatibility right..?
If we add strict version check, then backward compatibility will be broken. Am
I missing something..?
{quote}
I don't think it is compatibility. Compatibility means your new code could read
old cookie format and do the right thing.
if there is instanceid existed in ZooKeeper, which means it is format using
bookie.format, so all the old data has been removed. if you using an old cookie
(version 3) to access a new instance (same as you use a old instance id access
a new instance id), why not fail it?
> Create Bookie format command
> ----------------------------
>
> Key: BOOKKEEPER-300
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-300
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-server
> Affects Versions: 4.1.0
> Reporter: Rakesh R
> Attachments: BOOKKEEPER-300.patch, BOOKKEEPER-300.patch
>
>
> Provide a bookie format command. Then the admin would just have to run the
> command on each machine, which will prepare the bookie env
> +Zookeeper paths (znodes):+
> - ledger's root path
> - bookie's available path
> +Directories:+
> - Journal directories
> - Ledger directories
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
