You can take over a cluster created by using CLI or OCP on the command line interface (CLI) to the current OCP console, and continue to maintain and manage the cluster on the current OCP console.
Prerequisites
You are logged in to OCP as a user with the ADMIN or ORG_ADMIN role.
All OBServer nodes of the OceanBase cluster to be taken over are running normally.
When you take over an OceanBase cluster, follow the principle of taking over the primary cluster first:
If you are in a single OCP scenario, take over the primary OceanBase cluster first, and then take over the standby OceanBase cluster.
If you are in a multi-OCP scenario, take over the primary OceanBase cluster in one OCP first, and then take over the standby OceanBase cluster in any OCP.
The service name of each tenant in the OceanBase cluster to be taken over must be unique, and the service name must also be unique in the system. Otherwise, after the takeover, the service name of the tenant in the OceanBase cluster will be set to Invalid. For more information about service names, see Manage service names.
If the OceanBase cluster to be taken over is deployed by using obd, check whether the cluster meets the takeover conditions by referring to Take over an obd-deployed cluster in OCP before the takeover.
Considerations
- After an OceanBase cluster is taken over, it cannot be maintained and monitored in the original OCP cluster. Therefore, assess the impact before the takeover.
- If the OceanBase cluster to be taken over has been configured with a load type, you must configure the load type again on the Overview page of the cluster after the takeover.
- When you take over an OceanBase cluster, OCP will also take over the corresponding host of each OBServer node in the cluster for unified management.
- If the credentials used by the hosts are the same, OCP can take over the hosts in the Precheck step.
- If the credentials used by the hosts are different, you must add the hosts to OCP by using the [Add Host] feature before you take over the cluster.
Procedure
Log in to the OCP console.
In the left-side navigation pane, click Cluster. The Clusters page automatically appears.
On the Clusters page, click Take over Cluster in the upper-right corner.
Connect to the cluster by using Direct Connection or OBProxy.
Direct Connection: Enter the Access URL and Port of the cluster, as well as the Root@sys Password. You can also choose to Enter proxyro Password. Click Next.
Note
The password of the proxyro account is used by OBProxy to access the OceanBase cluster. You can enter the password here to ensure consistency of the proxyro password. For more information about the proxyro account, see Manage proxyro accounts.
OBProxy: Enter the Access URL and Port of the cluster, as well as the Cluster Name, Cluster ID (Optional), and Root@sys Password. You can also choose to Enter proxyro Password. Click Next.
Note
- If the cluster to be taken over is a standby cluster, the cluster ID is required. If both the primary and standby clusters need to be taken over, take over the primary cluster first, and then the standby cluster.
- The password of the proxyro account is used by OBProxy to access the OceanBase cluster. You can enter the password here to ensure consistency of the proxyro password. For more information about the proxyro account, see Manage proxyro accounts.
After the cluster is connected, go to the precheck page.
If the precheck passes, you can enter the corresponding information and take over the hosts that correspond to the OBServer nodes that are not managed by OCP.
If the precheck fails, modify the OBServer node configurations as prompted and click Recheck after the modification.
Click Submit.
After the task is submitted, you can view the task execution progress on the submission result page or return to the cluster overview page.
Note
For OCP to connect to a database, the corresponding credential string must exist in Credential Management. After the cluster is taken over, you can import the cluster credential file obtained by using the Export Cluster feature into this OCP instance to facilitate the batch upload of cluster credentials. For more information, see Import Credentials.