Anonymitaet commented on a change in pull request #5237: [doc] Improve Pulsar Administration Upgrade URL: https://github.com/apache/pulsar/pull/5237#discussion_r326614886
########## File path: site2/docs/administration-upgrade.md ########## @@ -108,18 +106,18 @@ Before upgrading, you have to decide whether to upgrade the whole cluster at onc In a rolling upgrade scenario, upgrade one bookie at a time. In a downtime upgrade scenario, shut down the entire cluster, upgrade each bookie, and then start the cluster. -While upgrading in both scenarios, the procedure is the same for each bookie. +While you upgrade in both scenarios, the procedure is the same for each bookie. 1. Stop the bookie. 2. Upgrade the software (either new binary or new configuration files). 2. Start the bookie. > **Advanced operations** -> When upgrading a large BookKeeper cluster in rolling upgrade scenario, it is slow to upgrade one bookie at a time. If you have configured rack-aware or region-aware placement policy, you can upgrade bookies rack by rack or region by region. It speeds up the whole upgrade process. +> When you upgrade a large BookKeeper cluster in rolling upgrade scenario, upgrading one bookie at a time is slow. If you configure rack-aware or region-aware placement policy, you can upgrade bookies rack by rack or region by region, which speeds up the whole upgrade process. Review comment: ```suggestion > When you upgrade a large BookKeeper cluster in a rolling upgrade scenario, upgrading one bookie at a time is slow. If you configure rack-aware or region-aware placement policy, you can upgrade bookies rack by rack or region by region, which speeds up the whole upgrade process. ``` ---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
