This topic describes how to switch a follower OCP cluster to a leader in a failover. When the leader OCP cluster is unavailable, you can switch a follower to a leader in a failover.
Applicability
This topic applies only to OceanBase Cloud Platform Enterprise Edition. OceanBase Cloud Platform Community Edition does not support the multi-cluster mode.
Background
When the leader OCP is unavailable, you can select a follower based on your business requirements and switch it to a leader in a failover. After the failover is completed, the follower OCP cluster becomes a leader of all OCP clusters connected to it. For more information about the failover, see OCP multi-cluster mode.
Prerequisite
- You have logged in to the OceanBase Cloud Platform (OCP) console and been assigned the ADMIN role.
- All follower OCP clusters are operating properly.
Procedure
Log on to the OCP console.
In the left-side navigation pane, choose System Management > OCP Multi-cluster Mode .
In the
Current OCP Basic Information section of the Leader & Follower Details tab, clickSwitch to Leader OCP .
Click Switch Disaster Recovery .
After the failover is completed, choose System Management > Tasks in the left-side navigation pane and view the task progress. For more information, see Manage tasks.
What to do next
After the failover is completed, perform one of the following steps based on the status of the OCPs list of the leader OCP cluster:
The original leader OCP becomes a follower that has a heartbeat timeout exception. Therefore, you must manually delete information of the original leader OCP. For more information, see Delete a faulty follower OCP cluster.
The original leader OCP cluster recovers. Therefore, you must delete information of other OCP clusters from the original leader OCP cluster, change the role of the original leader to a follower, and then bind it to the new leader. For more information, see Delete a faulty follower OCP cluster and Register an OCP cluster.