Changing Standby DNs to Log Nodes (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.

Precautions

• This function is only available to distributed instances whose deployment model is 1 primary + 2 standby and version is V2.0-3.200.0 or later.
• PITR backup is suspended during the process of changing standby DNs to log nodes and automatically resumes after the operation is complete.
• After standby DNs are changed to log nodes, a full backup is automatically performed.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select the desired region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB.
4. On the Instances page, click the name of the target instance to go to the Basic Information page.
5. In the Node List area, click Change to Log Nodes.
   Figure 1 Changing the deployment model to 1 primary + 1 standby + 1 log
   

6. In the Change Standby Data Nodes to Log Nodes dialog box, select an AZ and click OK.
7. 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.