Access Keys:
Skip to content (Access Key - 0)


The selected root page could not be found.

Installing a Patch Release

Print this page

What is the best practice for installing a patch release?

A patch release is an upgrade for the same version of Rhino. Versions are indicated to one decimal point — for example Rhino version 2.0_01 or version 2.1_01. A patch release is an upgrade to the characters after the underscore, for example, from version 2.1_01 to 2.1_02.

This process is not relevant for major upgrades, only patch releases.

Recommended approach: parallel-cluster upgrade

The recommended approach for installing a patch release is a parallel-cluster upgrade: you install the patch version of Rhino alongside the existing cluster, by forming a new cluster and migrating the nodes, one by one, from the old cluster into the new cluster. This is an online approach that maintains service availability throughout the upgrade. The process includes in four stages:

Pre-upgrade checklist

Before starting the upgrade process:
Make sure you have a test system.
Use the test system to test and practice the upgrade process (before executing it live).
Suspend provisioning to the cluster during upgrade.
Don't upgrade during peak hours.
Take your time - the recommended approach is online - so you don't need to rush in order to minimise downtime (as there isn't any)

Sample cluster — before and after

Below are diagrams showing a sample cluster before and after upgrading with a patch release.

Adaptavist Theme Builder Powered by Atlassian Confluence