ivankelly commented on issue #1971: DNM/RFC ISSUE-1967: make ledger creation and removal robust to zk connection loss URL: https://github.com/apache/bookkeeper/pull/1971#issuecomment-576571314 I don't think it would be a bad thing to switch CURRENT version back to 2, but then we need a way for clients to change it to 3. I think a method for clients to change it to change the default metadata version is necessary anyhow. Lets say you want to upgrade from 4.9 to 4.10, and you're well aware of this change. You want to upgrade in a way that you can possibly rollback. There's a lot of changes in 4.10, so it would be nice to be able upgrade to 4.10 without default metadata version at 2, burn in the new version for a while, and then when you see 4.10 is ok, flip the switch up start using binary metadata. I think a user configuration for this is the best option. Clusterwise upgrade to 2->3 creates another big jumping off point. We would also need a tool to roll back binary ledgers to format 2 in case everything goes to hell.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
