An OceanBase cluster can be upgraded by using an upgrade script. The upgrade process is transparent to applications, so no cooperation from the applications is needed during the upgrade. The OceanBase cluster is upgraded zone by zone. During the upgrade, the leader partitions are actively switched from one zone to another, and the business in the zone to be upgraded is migrated to other zones.
This topic describes the upgrade limitations, considerations, and paths of OceanBase Database.
Notice
OceanBase Database V4.3.x cannot be upgraded from V4.2.x or earlier.
Limitations
When upgrading an OceanBase cluster, observe the following limitations:
- DDL is disabled: DDL is disabled during some stages of the upgrade. It will be automatically enabled after the upgrade is complete.
major freezeis disabled: When upgrading between some versions, major compactions are disabled. It will be automatically enabled after the upgrade is complete.- Replication and load balancing are disabled: When upgrading between some versions, replica migration and load balancing are disabled.
- Physical backup and restore are disabled: During an upgrade, baseline backups (log archives) are continuously generated but physical restore is disabled.
- Creating tenants is disabled.
Notice
If the OceanBase cluster is associated with the arbitration service, make sure to upgrade the arbitration service to version V4.1 or later before upgrading the OceanBase cluster. For more information, see Upgrade the arbitration service.
You can query the oceanbase.DBA_OB_ARBITRATION_SERVICE system view in the sys tenant to check whether the OceanBase cluster is associated with the arbitration service.
Considerations
When upgrading an OceanBase cluster, observe the following considerations:
Log archiving is suspended during the upgrade from OceanBase Database V4.0 to V4.1.
Contact a technician for assistance if the upgrade requires you to perform
ADD SERVERorDELETE SERVERoperations.You cannot directly upgrade a transition version. Refer to the upgrade version sequence in the
oceanbase_upgrade_dep.ymlfile.You must directly connect to the observer process where the Root Service is located to perform the upgrade, not through OceanBase Database Proxy (ODP).
Back up the following parameters before the upgrade, as they may be modified during the upgrade:
Starting from V4.3.0 Beta, OceanBase Database no longer supports the zlib_1.0 compression algorithm. The following checks are performed before the upgrade:
- The
zlibcompression algorithm cannot be used as the value of thelog_transport_compress_funcparameter during the upgrade. Please use another compression algorithm instead ofzlib. - If the
zlibcompression algorithm is used for any table during the upgrade, you need to replace it with another supported compression algorithm or disable compression. - The
zlibcompression algorithm cannot be used as the compression algorithm for connecting to an OBKV-Table during the upgrade. Please set thetableapi_transport_compress_funcparameter to a supported compression algorithm.
- The
Upgrade procedure
The upgrade script in OceanBase Database V4.x depends only on the Python scripts in the target version RPM package. Specifically, if the target version is V4.1.0 or later, only one upgrade procedure is followed, and only the OceanBase RPM package of the target version is needed. After decompressing the OceanBase RPM package, you will find the oceanbase_upgrade_dep.yml file, which records the version upgrade topology of OceanBase Database.
For more information, see the Step 2: Confirm the upgrade procedure section in Upgrade an OceanBase cluster.
Upgrade notes
- Upgrade from V4.3.0 Beta to V4.3.1 Beta is supported.
- Upgrade from the V4.2.x series or earlier versions to V4.3.1 Beta is currently not supported. As the versions evolve, support for upgrading from V4.2.x to V4.3.x will be added in the future.
Next steps
References
For information about how to upgrade an OceanBase cluster using OceanBase Cloud Platform (OCP), see Upgrade versions.