OceanBase Database supports cluster upgrades using upgrade scripts. The entire upgrade process is transparent to applications, which do not need to perform any stop-write or stop-service operations on the server side. OceanBase Database upgrades clusters in the order of zones. During the upgrade, the partition leader will actively switch between zones and redirect the business traffic of the zone to be upgraded to other zones for execution.
This topic describes the limitations, considerations, and upgrade paths for upgrading OceanBase Database.
Notice
OceanBase Database does not support upgrading from V4.2.x or earlier versions to V4.3.x.
Limitations
When you upgrade an OceanBase cluster, note the following limitations:
- DDL operations are disabled during some stages of the upgrade. They are enabled after the upgrade is completed.
major freezeis disabled during some stages of the upgrade. It is enabled after the upgrade is completed.- Migration replication and load balancing are disabled during some stages of the upgrade.
- Physical backup and restore are disabled during the upgrade.
- New tenants cannot be created during the upgrade.
Notice
If the cluster is associated with an arbitration service, you must upgrade the arbitration service before you upgrade the cluster. For more information, see Upgrade the arbitration service.
You can query the oceanbase.DBA_OB_ARBITRATION_SERVICE view in the sys tenant to check whether the cluster is associated with an arbitration service.
Considerations
When you upgrade an OceanBase cluster, note the following considerations:
Log archiving is disabled during the upgrade from OceanBase V4.0 to V4.1.
If you need to perform
ADD SERVERorDELETE SERVERoperations during the upgrade, contact Technical Support.You cannot directly upgrade from an intermediate version of OceanBase. You must follow the upgrade sequence specified in the
oceanbase_upgrade_dep.ymlfile.You must directly connect to the observer process that hosts the Root Service to run the upgrade script. You cannot use OceanBase Database Proxy (ODP) to connect.
You must back up the following parameters before the upgrade:
Starting from OceanBase Database V4.3.0 Beta, OceanBase Database no longer supports the zlib_1.0 compression algorithm. During the upgrade, the following checks are performed:
- The
zlibcompression algorithm is no longer supported as the value of thelog_transport_compress_funcparameter. You must use another compression algorithm instead. - If some tables use the
zlibcompression algorithm, you must replace the compression algorithm with another supported one or disable compression during the upgrade. - The
zlibcompression algorithm is no longer supported as the value of thetableapi_transport_compress_funcparameter. You must use another compression algorithm instead.
- The
If a cluster based on an ARM architecture or an x86 architecture that does not support the AVX2 (Advanced Vector Extensions 2) instruction set contains columnstore tables (either original columnstore tables or columnstore tables converted to rowstore tables), you cannot upgrade the cluster from a lower version of V4.3 (V4.3.0, V4.3.1, or V4.3.2) to V4.3.3 or later. This is to prevent data correctness risks after the upgrade.
If you upgrade a cluster of a lower version of V4.3 to a cluster of V4.3.3 or later, the standby tenant cannot parse the logs generated by the upgraded cluster. An error is returned when the standby tenant submits logs (the error is not persisted). For more information about data recovery, see Prepare for data recovery.
Tenants backed up in a cluster of V4.3.2 cannot be restored in a cluster of V4.3.3.
Starting from V4.2.5 BP3, V4.2.5 BP4, V4.2.5 BP5, V4.3.5 BP1, V4.3.5 BP2, and V4.3.5 BP3, the instruction set requirements for x86 architectures are updated. The OBServer process checks whether the current environment supports the AVX instruction set before it starts. If the AVX instruction set is not supported, the OBServer process cannot start. Upgrading an OBServer process running on an x86 architecture that does not support the AVX instruction set to one of the above versions will result in the process being unable to start and will not support rollback. Please pay attention to this.
Note
Starting from the following versions, OceanBase Database no longer strictly requires the AVX instruction set:
- Starting from V4.3.5 BP4, the AVX instruction set is no longer required for V4.3.5.
- Starting from V4.2.5 BP6, the AVX instruction set is no longer required for V4.2.5.
- Starting from V4.4.1, the AVX instruction set is no longer required for V4.4.0.
Upgrade considerations
- You can upgrade from any V4.3.x version to V4.3.5 BP6.
- You cannot upgrade from a V4.2.x version or a lower version to V4.3.5 BP6.
- Starting from V4.3.2, the persistence format of multi-source data has been restructured. During the upgrade, the new and old formats of multi-source data must be converted. Sufficient upgrade time must be reserved when the number of partitions is large.
- For scenarios with continuous vector writes, index rebuilding is required.
- During the mixed deployment of V4.3.0/V4.3.1/V4.3.2 to V4.3.5 BP5, if the tenant leader is on the old node, the transfer will fail. You must upgrade to V4.3.5 BP5 to execute the transfer.
Upgrade path
Note
- This diagram shows the upgrade path for SN mode only. For more information about the upgrade paths of other versions, refer to
oceanbase_upgrade_dep.yml, which records the topology of OceanBase version upgrades. - After decompressing the target version's OceanBase RPM package, two directories named
homeanduseare created in the RPM package storage directory. The upgrade-related scripts and theoceanbase_upgrade_dep.ymlfile are stored in thehome/admin/oceanbase/etcdirectory.
oceanbase_upgrade_dep.yml file to confirm the upgrade path, see the Step 2: Verify the upgrade process section in Upgrade OceanBase Database.
The diagram explains as follows:
For versions of V4.2.x:
- V4.0.0.0, V4.1.0.0, V4.1.0.2, and V4.2.0.0 can be upgraded to V4.2.1.11 and then to V4.2.5.7.
- V4.2.2 to V4.2.4 can be directly upgraded to V4.2.5.7 or first upgraded to V4.2.5.0 to V4.2.5.6 and then to V4.2.5.7.
- V4.2.5 BP7 can be directly upgraded to V4.4.2 or V4.4.2.1.
- Barrier versions: V4.2.1.11, V4.2.5.7.
For versions of V4.3.x:
- All versions of V4.3.x can be directly upgraded to V4.3.5.6.
- V4.3.5.6 can be upgraded to V4.4.2.1.
- Upgrades from V4.2.x or earlier to V4.3.x are not supported.
- Barrier versions: V4.3.5.6.
For versions of V4.4.x:
- V4.4.0 and V4.4.1 can be directly upgraded to V4.4.2 or V4.4.2.1.
- V4.4.0 and V4.4.1 can be directly upgraded to V4.6.0.
For versions of V4.5.x:
- V4.5.0 can be upgraded to V4.6.0.
What to do next
References
For information about how to upgrade an OceanBase cluster by using the OceanBase Cloud Platform (OCP), see Upgrade OceanBase Database.