This topic describes how to change the primary zone for a PolarDB-X instance whose nodes are deployed in three zones. This topic also describes how to resolve the issue in which specific leader nodes are not deployed in the primary zone of the instance.
Change the primary zone of an instance
How to resolve the issue in which specific leader nodes are not deployed in the primary zone of the instance
- Q: The system uses data nodes of an instance in high availability mode. As a result, specific data nodes that are not deployed in the primary zone of the instance are used as leader data nodes.
- A: To resolve this issue, click Specify Primary Zone in the Topological information section on the Basic information page of the instance. In the Primary Zone drop-down list, select the ID of the primary zone of the instance and click OK.
The status of the instance changes to HA switching. After the status of the instance becomes Running, you can view that the zones of all leader data nodes and Global Meta Service (GMS) nodes are the same as the primary zone of the instance.
Notice Primary zone change operations cause transient connections. We recommend that you change the primary zone during off-peak hours.