Deleting Coordinator Nodes for an Instance (Distributed)

Scenarios

As service demand decreases, some CNs are left idle. To improve resource utilization, you can delete unnecessary coordinator nodes. This function is available only for distributed GaussDB instances that are deployed independently.

Precautions

• Deleting CNs does not interrupt ongoing services.
• You can only delete the CNs of instances that were deployed independently.
• At least one CN needs to be reserved for each DB instance.
• Before deleting a CN, ensure that the CN is not in a JDBC connection configuration, or the high availability of the JDBC connection may be affected.
• DDL operations will be rolled back when CNs are being deleted.
• PITR backup is suspended during the deletion and is automatically restored after deletion is complete.
• After the deletion is complete, a full backup is performed automatically.
• Before you delete CNs, you need to ensure that the instance status and all CNs are normal.
• Main processes are running on the main CN (that is, the CN whose component ID is cn_5001), so this CN cannot be deleted for scale-in. You can call the Querying the Components of a DB Instance API to query cn_5001. If the CN to be deleted is cn_5001, the system will randomly select another CN to delete.

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 delete CNs.
5. In the DB Information area of the Basic Information page, delete CNs.
   1. Click Delete next to Coordinator Nodes.
   2. Select the coordinator nodes to be deleted.
      Figure 1 Deleting CNs
      

   3. Click Next.
   4. Confirm the information about the CNs to be deleted and click Submit.