OceanBase Database allows you to upgrade a cluster by using an upgrade script. 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.
This topic describes the upgrade limitations, considerations, and upgrade paths for OceanBase Database.
Notice
OceanBase Database currently does not support upgrading from the V4.2.x series or earlier versions to V4.3.x.
Upgrade limitations
Pay attention to the following limitations when you upgrade an OceanBase cluster:
- DDL is disabled in some phases of the upgrade and is automatically enabled after the upgrade.
- Major freezes are disabled during the upgrade between some versions and are automatically enabled after the upgrade.
- Migration, replication, and load balancing are disabled during the upgrade between some versions.
- During the upgrade of a cluster, physical baseline backup and physical restore are not allowed, but log archiving is not interrupted.
- New tenant cannot be created during the upgrade process.
Notice
If the OceanBase cluster is associated with an arbitration service, you must upgrade the arbitration service version before upgrading the OceanBase cluster version. For detailed instructions on upgrading the arbitration service, see Upgrade the arbitration service.
You can use the system tenant view oceanbase.DBA_OB_ARBITRATION_SERVICE to check whether the current OceanBase cluster is associated with an arbitration service.
Considerations
When you upgrade an OceanBase cluster, note that:
During the upgrade from OceanBase V4.0 to V4.1, log archiving will be suspended.
If the
ADD SERVERorDELETE SERVERoperation needs to be performed during the upgrade, contact OceanBase Technical Support.Transition versions cannot be directly upgraded, but need to be upgraded by following the upgrade path.
The upgrade script must be executed by directly connecting to the observer process where the Root Service resides. It cannot be executed through OceanBase Database Proxy (ODP).
The following parameters may be modified during the upgrade. Therefore, back up these parameters before the upgrade.
Starting from V4.3.0 Beta, OceanBase Database no longer supports the
zlib_1.0compression algorithm. Observe the following rules during an upgrade:- The
zlibcompression algorithm is no longer supported for thelog_transport_compress_funcparameter. Use another compression algorithm instead. - If the
zlibcompression algorithm is used for any tables, replace it with another supported compression algorithm or disable compression during the upgrade. - The
zlibcompression algorithm is not supported for OBKV-Table. You can specify another compression algorithm for OBKV-Table by using thetableapi_transport_compress_funcparameter.
- The
In clusters using Arm-based servers or x86-based servers that do not support Advanced Vector Extensions 2.0 (AVX2) instructions, if columnstore tables have been used in OceanBase Database V4.3.0, V4.3.1, or V4.3.2, upgrading to V4.3.3 or later is not supported to prevent potential data correctness risks after the upgrade.
When you upgrade an OceanBase cluster from a version earlier than 4.3.3 to V4.3.3 or later, the earlier version cannot parse the logs generated by standby tenants in the target version. In this case, an error is returned when the standby tenants attempt to commit logs. However, the logs are not persisted. For more information about data restore, see Preparations.
Tenants backed up in a V4.3.2 cluster cannot be restored in a V4.3.3 cluster.
Instruction set requirements for running in x86 architecture environments were introduced in versions 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. Before startup, the OBServer process checks whether the current environment supports the AVX instruction set. If AVX is not supported, OBServer will not start. Upgrading older versions of OBServer on x86 machines that lack AVX support to any of these versions will result in startup failure, and rollback will not be possible. Please pay close attention to this issue.
Note
Starting from the following versions, OceanBase Database no longer requires support for the AVX instruction set:
- For V4.3.5, beginning with V4.3.5 BP4.
- For V4.2.5, beginning with V4.2.5 BP6.
- For V4.4.0, beginning with V4.4.1.
Upgrade notes
- Upgrades from any V4.3.x version to V4.3.5 BP3 are supported.
- Upgrades from the V4.2.x series or earlier versions to V4.3.5 BP3 are not supported.
- Starting with V4.3.2, the persistence format for multi-source data has been restructured. During the upgrade process, the system must convert between the old and new formats. For clusters with a large number of partitions, ensure you allocate sufficient time for the upgrade.
- For vector scenarios with continuous writes, index reconstruction is required.
- When upgrading from V4.3.0 or V4.3.1 to V4.3.5 BP3, you must stop the transfer task one day in advance. Run
alter system set enable_transfer = False;to stop the task, and then set it toTrueafter the upgrade. - During the upgrade from V4.3.0, V4.3.1, or V4.3.2 to V4.3.5 BP3, if the tenant leader is located on the old node, the transfer will fail. You must upgrade to V4.3.5 BP3 to perform the transfer.
Upgrade path diagram
Note
- This upgrade path diagram does not include all OceanBase Database versions. For more details about upgrade paths, refer to the
oceanbase_upgrade_dep.ymlfile, which outlines the complete version upgrade topology for OceanBase. - After extracting the RPM package for the target version of OceanBase, two directories,
homeanduse, will be created in the directory where the RPM package is stored. The upgrade scripts and theoceanbase_upgrade_dep.ymlfile are located in thehome/admin/oceanbase/etcdirectory.
oceanbase_upgrade_dep.yml file to confirm the upgrade path, see the section Step 2: Confirm the Upgrade Process in Upgrade an OceanBase cluster.
Explanation of the upgrade path diagram:
V4.2.x upgrade path:
- Versions from V4.2.1.2 to V4.2.1.9 can be upgraded to V4.2.1.10, and then further upgraded to V4.2.5.1.
- Versions from V4.2.1.2 to V4.2.1.9 can also be upgraded to V4.2.1.11, and then further upgraded to V4.2.5.3 and later versions in the V4.2.5 series.
- Barrier versions: V4.2.1.2, V4.2.1.10, and V4.2.1.11.
V4.3.x upgrade path:
- All V4.3.x versions can be upgraded to the next general availability (GA) version, eventually reaching V4.3.5.
- All V4.3.x versions can also be upgraded directly to V4.3.5.
- Backups in V4.3.2 cannot be restored in V4.3.3.
What to do next
References
For more information about how to upgrade an OceanBase cluster by using OceanBase Cloud Platform (OCP), see Upgrade an OceanBase cluster.