Adding Shards for an Instance (Distributed)

Scenarios

As the instance deployment time and data increase, the database performance and storage will gradually reach the bottleneck. In this case, you need to add hosts to improve the instance performance and storage capability. This function is available only 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.

• Instances can be scaled out only when they are in the Available state. During shard scale-out, you can still query and insert data, query services are not interrupted, and the data insertion performance is not affected. The performance of join queries on local tables across node groups during redistribution may be affected.

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 target instance.
5. On the Basic Information page, click Add in the Shards field.
   Figure 1 Adding shards
   

6. Specify the number of shards to be added. Click Next.
   Figure 2 Adding shards
   

7. Confirm the information and then click Submit.
   

   By default, a shard contains three replicas (a primary DN and two standby DNs). Each time you add a shard, three replicas will be added.