Adding Coordinator Nodes for an Instance (Distributed)

Scenarios

As the instance deployment time and data increase, the database performance and storage will gradually reach the bottleneck. Adding nodes can improve the instance performance and storage capacity. You can only add nodes for distributed GaussDB instances that are deployed independently.

• The scaling duration depends on the amount of data. The default timeout period is seven days. When nodes are being added, the instance is available, but you are not allowed to perform other operations on the console. If you need to perform any operations, contact customer service.
• You can flexibly add CNs or shards as needed. It is recommended that the number of CNs of a DB instance do not exceed twice the number of shards.

• Instances can be scaled out only when they are in the Available state.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a 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 instance for which you want to add nodes.
5. On the Basic Information page, click Add in the Coordinator Nodes field.
6. Specify the number of coordinator nodes to be added and the AZ.
   Figure 1 Adding coordinator nodes
   

   If single-AZ deployment is specified during the instance creation, CNs are only added to the AZ you specified.

7. Click Next.
8. Confirm the information and click Submit.