Help Center/
GaussDB/
User Guide/
Instance Modifications/
Performing a Primary/Standby DN Switchover/
Performing a Primary/Standby Switchover
Updated on 2024-11-11 GMT+08:00
Performing a Primary/Standby Switchover
Scenarios
GaussDB supports primary/standby DN switchover in a shard of an instance when the instance is available. You can promote a standby DN to the primary DN in a shard.
Constraints
- This operation cannot be performed when the node status is abnormal.
- Only one standby node can be specified as the primary node in a shard.
- Single-node instances do not support primary/standby DN switchovers.
- During a primary/standby switchover, the following operations cannot be performed:
- Rebooting a DB instance
- Switching AZs
- Changing CPU and memory specifications of an instance
- Repairing a node
- Replacing a node
- Adding nodes
- Backing up and restoring an instance
Precautions
- Services may be interrupted for several seconds or minutes during the switchover. You are advised to perform this operation during off-peak hours.
- Switchovers will not change private IP addresses of an instance.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Click in the upper left corner of the page and choose .
- Click the target instance name to go to the Basic Information page.
- In the Node List area, click Switch Primary and Standby DNs.
- Select an AZ to view the DN shard of the primary DN in the selected AZ. Select the standby DN to be promoted to primary, enter rearrange, and click OK.
Figure 1 Switching primary and standby DNs
- If there is no primary DN in the selected AZ, shard information is not displayed.
- Services may be interrupted for several seconds or minutes during the switchover. You are advised to perform this operation during off-peak hours.
- Primary/standby switchover can be performed on a maximum of 30 shards at a time.
- Select the standby DN to be promoted to primary and click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot