This topic describes how to bind a standby OCP cluster to a primary OCP cluster when you log in to the standby OCP cluster for the first time in multi-cluster mode of OCP. If you are not in multi-cluster mode, skip this topic.
Prerequisites
You have created primary and standby OCP clusters in multi-cluster mode.
You have deployed the primary and standby OCP clusters by following the procedure in Install OCP.
To convert multiple single-node OCP clusters in standard mode to multi-cluster OCP, you can refer to Multi-cluster mode switch to convert one cluster into the primary cluster and convert the remaining single-node OCP clusters in standard mode into standby clusters.
Note
In this scenario, there must be no OceanBase primary clusters with the same name in the primary and standby OCP clusters.
You have obtained the JDBC connection information for the primary cluster's MetaDB.
Procedure
On the login page of the standby OCP cluster, enter the Username and Password, and click Log On.
The system enters the Welcome to Multi-cluster mode interface.
Enter the parameters in the Connection Information for Primary OCP MetaDB section.
ParameterDescriptionHost Address The IP address of the node where the primary OCP MetaDB resides. For example: xxx.xxx.xxx.xxx. Port The access port for the primary OCP MetaDB. For example: 2881. Username The username for accessing the primary OCP MetaDB. For example: ocp@ocp_meta#ocp321. Password The password for the user accessing the primary OCP MetaDB. For example: aA******1j . Database The database name of the primary OCP MetaDB. For example: meta_01. Note
The information in the table is the JDBC connection information for the MetaDB, which can also be used to access this MetaDB in the background. If binding to the primary OCP fails, you can use the following command to access this MetaDB in the background for basic troubleshooting.
###Execute the obclient command on the client to connect to the database server obclient -hxxx.xxx.xxx.xxx -P2881 -u<username>@<tenant name#cluster name> -paA******1j -Dmeta_01Click Bind to Leader OCP.
If the system switches to business mode, this standby OCP cluster is bound to the primary OCP cluster.
If this primary OCP cluster is also bound to other standby OCPs, due to the primary-standby data synchronization interval set by the
ocp.multi-cluster.replication.interval.secondsparameter, other standby OCPs may not be immediately displayed in the OCPs of this standby OCP. For details, see the description of OCPs in Primary-standby details page description.
