OceanBase Cloud Platform (OCP) supports Multi-node deployment and multi-cluster mode.
Deploy OCP cluster in the multiple nodes
In multi-node deployment, OCP is deployed on multiple nodes, each of which is deployed with all OCP components. The OCP components include OCP-Server, MetaDB, MonitorDB, and OBProxy. For more information about the deployment on each node, see the description of single-node deployment.
All OCP-Server nodes form a stateless service cluster. All MetaDB and MonitorDB nodes form a multi-replica cluster. OBProxies deployed on all nodes also form a stateless service cluster.
In multi-node deployment mode, when a minority of hosts or services on a minority of hosts are unavailable, the entire system is still available.
Note
Multi-node deployment applies to production environments with high requirements on system availability.
Deployment process
The procedure for deploying OceanBase Cloud Platform (OCP) on multiple nodes is similar to that for deploying OCP on a single node. The only difference is that you need to add multiple servers in the Add a server step.
Sequence |
Step |
Description |
|---|---|---|
| 1 | Plan resources | For more information, see OCP-Server specifications, MetaDB resources, MonitorDB resources, and Host resources. |
| 2 | Prepare the deployment environment | The deployment environment requirements cover the installation media, host resources, and system requirements. For more information, seeInstall OAT, Add a server and Host resources. |
| 3 | Deploy OCP | For more information, see Prepare installation media, Deploy metadb, Deploy OCP, and Initialize system parameters. |
| 4 | Check after deployment | After you deploy OCP, you can verify the installation by checking the OCP features, log files, OCP version, time, and Docker container. |
Deploy OCP clusters in the multi-cluster mode
In multi-cluster mode, you can deploy multiple OCP clusters across regions to manage primary and standby OceanBase clusters across regions. You can manage primary and standby OceanBase clusters across OCP clusters. For example, you can create, delete, and update primary and standby OceanBase clusters, and perform switchover and failover. This mode implements a high-availability redundancy architecture based on two IDCs.
High-availability deployment can provide disaster recovery across IDCs and regions. When services in one of the IDCs or regions are unavailable, the entire system is still available.
Note
High-availability deployment is commonly used in production environments that require disaster recovery across IDCs or regions.
Deployment process
The deployment process contains five steps: planning resources, preparing the environment, deploying a leader OCP cluster, deploying follower OCP clusters, and check after deployment, as described in the following table.
SN |
Step |
Description |
|---|---|---|
| 1 | Plan resources | For more information, see Configure the OCP server, MetaDB resources, MonitorDB resources and Host resources. |
| 2 | Prepare environment | For more information, see Install OAT, Add a server, and Check the environment. |
| 3 | Deploy a leader OCP cluster | For more information, see Prepare installation media, Create MetaDB, Deploy OCP and Initialize system parameters.
Notice |
| 4 | Deploy follower OCP clusters | For more information, see Prepare installation media, Create MetaDB, Deploy OCP, Register an OCP cluster, and Initialize system parameters. You can deploy multiple follower OCP clusters in the same way.
Notice |
| 5 | Check after deployment | After the deployment is completed, you can: 1. Check the OCP features, log files, OCP version, time, and Docker container to verify whether the leader and follower OCP clusters are properly deployed. For more information, see Check after deployment 2. If multi-cluster mode is enabled, log on to the OCP console. In the left-side navigation pane, choose System Management > OCP Multi-cluster Mode . On the page that appears, click the Leader & Follower Details tab and check the status of the leader and follower OCP clusters to verify whether the follower is bound to the leader. |