You can use OceanBase Cloud Platform (OCP) to upgrade an OceanBase cluster with a few clicks. The upgrade on the server side has no impact on applications, and can be performed without suspending data write or services.
OceanBase Database is upgraded zone by zone. During the upgrade, the leader role is switched from one zone to another, and the services running in the zone to be upgraded are migrated to other zones.
Upgrade path
You can directly upgrade OceanBase Database from V3.2.3.1 to V3.2.4.0. To upgrade from a version earlier than V3.1.2 to V3.2.4.0, you must upgrade the source version to the binary versions one by one in the following parts of the upgrade path:
V1.4.51 > V1.4.60 > V1.4.61 > V1.4.70 > V1.4.71 > V1.4.72 > V1.4.73 > V1.4.74 > V1.4.75 > V1.4.76 > V1.4.77 > V1.4.78 > V1.4.79 (binary)
V1.4.79 (binary) > V2.0.0 > V2.1.1> V2.1.11> V2.1.20 > V2.1.30 > V2.1.31 (binary)
V2.1.31 (binary) > V2.2.0 > V2.2.1 (binary)
V2.2.1 (binary) > V2.2.20 > V2.2.30 > V2.2.40 > V2.2.50 (binary)
V2.2.50 (binary) > V2.2.51 > V2.2.52 > V2.2.60 > V2.2.70 > V2.2.71 > V2.2.72 > V2.2.73 > V2.2.74 > V2.2.75 > V2.2.76 > V2.2.77 (binary)
V2.2.77 (binary) > V3.1.2 (binary)
V3.1.2 (binary) > V3.2.0 > V3.2.1 > V3.2.2 > V3.2.3.0 > V3.2.3.1 > V3.2.4.0
Note
Before the upgrade, you must upload RPM packages of all versions required in the upgrade path to OCP.
After the upgrade starts, OCP divides the upgrade process based on binary versions, and upgrades the cluster to each binary version zone by zone.
For example, to upgrade a cluster that contains three zones (zone1, zone2, and zone3) from V2.2.30 to v3.2.4.0, you can choose the following upgrade path:
V2.2.30 > V2.2.40 > V2.2.50 (binary) > V2.2.51 > V2.2.52 > V2.2.60 > V2.2.70 > V2.2.71 > V2.2.72 > V2.2.73 > V2.2.74 > V2.2.75 > V2.2.76 > V2.2.77 > V3.1.2 > V3.2.0 > V3.2.1 > V3.2.2 > V3.2.3.0 > V3.2.3.1 > V3.2.4.0
Before the upgrade, you must upload RPM packages of all versions required in the upgrade path to OCP. In this example, you need to upload the RPM packages of the following versions : V2.2.40, V2.2.50, V2.2.51, V2.2.52 , V2.2.60, V2.2.70, V2.2.71, V2.2.72, V2.2.73, V2.2.74, V2.2.75, V2.2.76, V2.2.77, V3.1.2, V3.2.0, V3.2.1, V3.2.2, V3.2.3.0, V3.2.3.1, and V3.2.4.0. OCP divides the upgrade process based on binary versions as follows:
V2.2.30 > V2.2.40 > V2.2.50 (binary)
V2.2.50 (binary) > V2.2.51 > V2.2.52 > V2.2.60 > V2.2.70 > V2.2.71 > V2.2.72 > V2.2.73 > V2.2.74 > V2.2.75 > V2.2.76> V2.2.77 (binary)
V2.2.77 (binary) > V3.1.2 (binary)
V3.1.2 (binary) > V3.2.0 > V3.2.1 > V3.2.2 > V3.2.3.0 > V3.2.3.1 > V3.2.4.0
According to the preceding upgrade path, OCP sequentially upgrades zone1, zone2, and zone3 from V2.2.30 to V2.2.50. In other words, the entire cluster is upgraded from V2.2.30 to V2.2.50 (binary). After that, OCP sequentially upgrades zone1, zone2, and zone3 from V2.2.50 (binary) to V2.2.77, and from V2.2.77 to V3.1.2. The process of the cluster upgrade ends when all zones are upgraded to V3.2.4.0.
Considerations
Take note of the following items when you upgrade an OceanBase cluster:
The whole cluster is upgraded. You cannot upgrade only a single zone.
The upgrade cannot be rolled back. You cannot downgrade from a later version to an earlier version.
When OceanBase Database is in the progress of an upgrade, data compaction, replication and migration, all business DDL statements, and some tenant DDL statements are disabled.
If the upgrade fails, do not retry. Contact OceanBase Technical Support.
Before you upgrade OceanBase Database to V3.2.4, set
_max_trx_sizeto 0.Note
_max_trx_sizespecifies the maximum size of a transaction. The default value is 100 MB. The value 0 indicates not limiting the size of a transaction._max_trx_sizedoes not take effect in versions earlier than OceanBase Database V3.2.4. In other words, the size of a transaction is not limited in versions earlier than V3.2.4.
Upgrade impact
An upgrade may have the following impacts:
The leader role is switched from one zone to another during the upgrade, which increases the response time (RT) a little bit.
The leader-follower switchover during the upgrade can affect your business. Transactions that exceed 100 ms are terminated.