OceanBase Cloud Platform (OCP) allows you to upgrade a standalone centralized OceanBase database to a distributed cluster online. This topic describes the procedure.
Background information
- After you upgrade a cluster to span multiple hosts in a single zone, only the computing capabilities of the cluster are improved. The cluster does not support multi-replica high availability and applies only to a development or test environment.
- If you upgrade a cluster to span an even number of zones, the cluster cannot meet the high availability requirements and has data security risks. We recommend that you adjust the configurations to ensure an odd number of zones or enable the arbitration service for the cluster or tenant.
Prerequisites
Make sure that you have the following permissions:
-
Resource Permissions : Cluster Maintenance permission -
Menu Permissions : Permission on theOverview menu ofClusters
-
You have deployed a standalone centralized OceanBase database.
Procedure
Log in to the OCP console.
In the left-side navigation pane, select
Clusters . TheClusters page automatically appears.On the
Clusters page, find the target cluster and click its name.On the
Overview page of the cluster, click Scale to a distributed cluster.In the panel that appears on the right, configure the following parameters.
Select a software package type. By default, the software package type is the same as the software installation package type of the current OceanBase cluster. If the system cannot identify the software installation package type of the OceanBase cluster, you need to select an appropriate installation package based on the version of your operating system.
By default, the system allows you to upgrade a cluster by adding zones. You can also upgrade a cluster by adding OBServer nodes. To do so, click the
Add OBServer Node tab and upgrade the cluster to span multiple hosts in a single zone.By default, the system allows you to upgrade a cluster by adding zones. You can also upgrade a cluster by adding OBServer nodes. To do so, click the Add OBServer Node tab and upgrade the cluster to span multiple hosts in a single zone.
Parameter Description Zone Name The name of the zone. IDC The IDC where the zone is located. Model Optional. If you select a model, the host list is filtered based on the model. CPU Architecture The CPU architecture of the host in the zone must be the same as that of the cluster.
After you select an architecture, the system checks whether an installation package for the CPU architecture of the current cluster exists. If the installation package for the specified architecture does not exist, the zone cannot be added.Software Package Type The type of the software installation package of the OceanBase cluster. If the system cannot identify the software installation package type of the OceanBase cluster, you need to select an appropriate installation package based on the version of your operating system. Host When you upgrade a cluster by adding zones, you can select only one host as the OBServer node and RootServer. When you upgrade a cluster by adding OBServer nodes, you can select multiple hosts. - If no host is available in the drop-down list, you can click
Add Host in the drop-down list to add one. For more information, see Add a host. - In a production environment, we recommend that the size of the log disk be at least three times the memory size of the host. To avoid performance issues, we recommend that you do not create the data directory and the log directory on the same disk.
Parameter Description Zone Name The name of the zone. IDC The IDC where the zone is located. Model Optional. If you select a model, the host list is filtered based on the model. CPU Architecture The CPU architecture of the host in the zone must be the same as that of the cluster.
After you select an architecture, the system checks whether an installation package for the CPU architecture of the current cluster exists. If the installation package for the specified architecture does not exist, the zone cannot be added.Host When you upgrade a cluster by adding zones, you can select only one host as the OBServer node and RootServer. When you upgrade a cluster by adding OBServer nodes, you can select multiple hosts. - If no host is available in the drop-down list, you can click Add Host in the drop-down list to add one. For more information, see Add a host.
- In a production environment, we recommend that the size of the log disk be at least three times the memory size of the host. To avoid performance issues, we recommend that you do not create the data directory and the log directory on the same disk.
Tenant Configuration Settings of tenants. You can configure replicas for multiple tenants in the cluster at a time. - You can specify the replica type, unit specification, and number of units.
- Each row contains parameters of only one tenant. To configure more tenants, click Add Tenant.
- The number of units is automatically specified based on the selected tenant and cannot be edited.
Note
- In addition to adding zones, you can also delete zones other than Zone1. You must retain at least one zone. Otherwise, you cannot upgrade the database to a distributed cluster.
- The name, IDC, model, CPU architecture, and host information of Zone1 cannot be modified.
- If no host is available in the drop-down list, you can click
Complete the custom settings. Specifically, configure the OS user, path, and port number of the OBServer node. For more information, see the section about custom settings in Create a distributed cluster.
Choose whether to select Add Replicas for All Tenants in the
Tenant Configuration section.If you select this option, replicas are added for all tenants in the cluster. The replica type, unit config, and unit quantity of each tenant are the same as those in the original zone.

Click
OK .In the dialog box that appears, you can click
View Task to view the task progress.You can also view the task progress in
Task Center .