OceanBase Database allows you to upgrade a cluster by using an upgrade script. The upgrade process is transparent to applications, which do not need to perform any stop-write or stop-service operations. OceanBase Database upgrades the cluster in the order of zones. During the upgrade, the leader of each partition is switched across zones, and the business traffic of the zone to be upgraded is redirected to other zones.
This topic describes the upgrade process, considerations, limitations, and impact of upgrading an OceanBase cluster.
Notice
OceanBase Database does not support in-place upgrades from versions earlier than V4.0.0 to V4.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 automatically after the upgrade is completed.
- The
major freezeoperation is disabled during some stages of the upgrade. It is enabled automatically 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. Physical baseline backup (log archive continues) and physical restore are not initiated.
- You cannot create a new tenant.
Notice
If the OceanBase cluster is associated with an arbitration service, you must upgrade the arbitration service before you upgrade the OceanBase 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 OceanBase 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 Database 4.0 to 4.1.
If the upgrade requires
ADD SERVER/DELETE SERVERoperations, contact technical support.You cannot directly upgrade from a transitional version. You must follow the upgrade sequence specified in the
oceanbase_upgrade_dep.ymlfile.The upgrade script must be executed directly on the observer process that hosts the Root Service. It cannot be executed through OceanBase Database Proxy (ODP).
The following parameters may change during the upgrade. You must back them up before the upgrade:
Starting from OceanBase Database V4.2.2, OceanBase Database no longer supports the zlib_1.0 compression algorithm. During the upgrade, the following pre-checks are performed:
- The
zlibcompression algorithm is no longer supported as the value of thelog_transport_compress_funcparameter. You must replace it with another compression algorithm. - If tables use the
zlibcompression algorithm, you must replace it with another supported compression algorithm or disable compression during the upgrade. - The
zlibcompression algorithm is no longer supported as the value of thetable_api_transport_compress_funcparameter. You must replace it with another compression algorithm.
- The
When you upgrade a V4.x cluster to a V4.2.5 or later cluster, 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).
If a cluster has a large number of tablets, the upgrade process may take a long time to restart the OBServer. For example, if a cluster has 3 million tablets, the restart process may take about 20 minutes. In such cases, you must reserve sufficient time for the upgrade.
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, OceanBase Database requires the AVX instruction set to run in an X86 environment. 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 that does not support the AVX instruction set to the above versions may result in failure to start or roll back. Please pay attention to this.
Note
Starting from the following versions, OceanBase Database no longer requires the AVX instruction set to run in an X86 environment:
- 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.
You cannot upgrade a backup of OceanBase Database V4.3.2 to OceanBase Database V4.3.3. You cannot restore a backup of OceanBase Database V4.3.2 to OceanBase Database V4.3.3.
Upgrade considerations
- You can upgrade OceanBase Database V4.2.1 BP10 to V4.2.5 BP7 by first upgrading it to V4.2.1 BP11.
- You can upgrade OceanBase Database V4.2.2 to V4.2.5 BP7 by first upgrading it to V4.2.2.1.
- You can directly upgrade OceanBase Database V4.2.3, V4.2.4, and V4.2.5 to V4.2.5 BP7.
Upgrade path
Note
- The upgrade path in this topic applies only to the SN series. To learn about the upgrade paths for other versions, you can refer to the
oceanbase_upgrade_dep.ymlfile. This file records the version upgrade path for OceanBase Database. - After you decompress the RPM package of the target version, two directories,
homeanduse, are created in the directory where the RPM package is stored. The upgrade-related scripts and theoceanbase_upgrade_dep.ymlfile are stored in thehome/admin/oceanbase/etcdirectory.
The following table describes the upgrade path:
V4.2.x:
- V4.0.0.0/V4.1.0.0-V4.1.0.2/V4.2.0.0 can be upgraded to V4.2.1.11 and then to V4.2.5.7.
- V4.2.2-V4.2.4 can be directly upgraded to V4.2.5.7, or first upgraded to V4.2.5.0-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 version: V4.2.1.11 and V4.2.5.7.
V4.3.x:
- All V4.3.x versions can be directly upgraded to V4.3.5.6.
- V4.3.5.6 can be upgraded to V4.4.2.1.
- V4.2.x and earlier versions cannot be directly upgraded to V4.3.x.
- barrier version: V4.3.5.6.
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 also be directly upgraded to V4.6.0.
V4.5.x:
- V4.5.0 can be upgraded to V4.6.0.
What to do next
References
For more information about how to upgrade an OceanBase cluster by using the OceanBase Cloud Platform (OCP), see Upgrade version.