Changing the 1 Primary + 2 Standby Deployment Model to 1 Primary + 1 Standby + 1 Log for a Distributed Instance
Scenarios
If the 1 primary + 2 standby deployment model of a distributed GaussDB instance does not meet service requirements, you can change the deployment model to 1 primary + 1 standby + 1 log.
Constraints
This function is only available to distributed instances whose deployment model is 1 primary + 2 standby and version is 3.200.0 or later.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project.
- Click
in the upper left corner of the page and choose .
- On the Instances page, click the name of the target instance to go to the Basic Information page.
- In the Node List area, click Change to Log Nodes.
Figure 1 Changing the deployment model to 1 primary + 1 standby + 1 log
- In the Change Standby Data Nodes to Log Nodes dialog box, select an AZ and click OK.
- Check the change result.
After the task is submitted, click Back to DB Instance List. On the Instances page, the instance status is Changing to log node. After the task is complete, go to the Basic Information page of the instance and check that the deployment model is changed to 1 primary + 1 standby + 1 log.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot