Help Center/ GaussDB/ User Guide/ Instance Modifications/ Changing the Deployment Model/ Changing Log Nodes to Standby DNs (for a Distributed Instance)
Updated on 2025-08-18 GMT+08:00

Changing Log Nodes to Standby DNs (for a Distributed Instance)

Scenarios

Each shard of a distributed GaussDB instance consists of one primary DN, one standby DN, and one log node. However, this architecture may not meet your application requirements. GaussDB provides the flexibility to convert the log node in each shard into a standby DN.

Constraints

  • This function is only available for distributed instances of V2.0-3.200.0 or later that have one primary DN, one standby DN, and one log node in each shard.
  • The statuses of the instance, cluster, and DNs must all be normal. If there is an error, rectify the fault before performing this operation.
  • After the deployment model of a yearly/monthly distributed instance is changed to 1 primary + 2 standby, you need to pay for the order in the order center.

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 1 Primary + 2 Standby.
  6. In the Change Log Nodes to Standby Data Nodes dialog box, 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 standby DN. 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 + 2 standby.