lucperkins commented on a change in pull request #403: Issue 355: upgrade guide URL: https://github.com/apache/bookkeeper/pull/403#discussion_r131715954
########## File path: site/docs/latest/admin/upgrade.md ########## @@ -0,0 +1,73 @@ +--- +title: Upgrade +--- + +> If you have questions about upgrades (or need help), please feel free to reach out to us by [mailing list](/community/mailing-lists) or [Slack Channel](/community/slack). + +## Overview + +Consider the below guidelines in preparation for the upgrade. + +- Always back up all your configuration files before upgrading. +- Read through the documentation and draft an upgrade plan that matches your specific requirements and environment before starting the upgrade process. + Put differently, don't start working through this guide on a live cluster. Read guide entirely, make a plan, then execute the plan. +- Pay careful consideration to the order in which components are upgraded. In general, you need to upgrade `bookies` first and then upgrade your clients. +- If `autorecovery` is running along with `bookies`, you need to pay attention to upgrade sequence. +- Read the release notes carefully for each release. They contain not only information about noteworthy features, but also changes to configurations + that may impact your upgrade. +- Always upgrade one or small set of `bookies` to canary new version before upgraing all `bookies` in your cluster. + +## Canary + +It is wise to canary a upgraded version in one or small set of `bookies` before upgrading all `bookies` in your live cluster. Review comment: an upgraded version ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
