Downgrade StarRocks
This topic describes how to downgrade your StarRocks cluster.
If an exception occurs after you upgrade a StarRocks cluster, you can downgrade it to the earlier version to quickly recover the cluster.
Overview
Review the information in this section before downgrading. Perform any recommended actions.
Downgrade paths
-
For patch version downgrade
You can downgrade your StarRocks cluster across patch versions, for example, from v2.2.11 directly to v2.2.6.
-
For minor version downgrade
For compatibility and safety reasons, we strongly recommend you downgrade your StarRocks cluster consecutively from one minor version to another. For example, to downgrade a StarRocks v2.5 cluster to v2.2, you need to downgrade it in the following order: v2.5.x --> v2.4.x --> v2.3.x --> v2.2.x.
-
For major version downgrade
You can only downgrade your StarRocks v3.0 cluster to v2.5.3 and later versions.
- StarRocks upgrades the BDB library in v3.0. However, BDBJE cannot be rolled back. You must use BDB library of v3.0 after a downgrade.
- The new RBAC privilege system is used by default after you upgrade to v3.0. You can only use the RBAC privilege system after a downgrade.
Downgrade procedure
StarRocks' downgrade procedure is the reverse order of the upgrade procedure. Therefore, you need to downgrade FEs first and then BEs and CNs. Downgrading them in the wrong order may lead to incompatibility between FEs and BEs/CNs, and thereby cause the service to crash. For FE nodes, you must first downgrade all Follower FE nodes before downgrading the Leader FE node.
Before you begin
During preparation, you must perform the compatibility configuration if you are up for a minor or major version downgrade. You also need to perform the downgrade availability test on one of the FEs or BEs before downgrading all nodes in the cluster.