Deleting Coordinator Nodes for an Instance (Distributed)

Scenarios

As service demand decreases, some coordinator nodes (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.

Billing

Billing Mode	Impact on Fees
Yearly/Monthly	After a CN is deleted, the system will stop charging you for it in the original subscription period. GaussDB refunds the difference in price based on the remaining period. Example (The prices below are for reference only. The actual prices are displayed on the console.) Suppose you purchased a one-month, enterprise-edition distributed instance of V2.0-8.210 (configurations: 3 shards, 3 replicas, 3 CNs; instance specifications: dedicated, 8 vCPUs \| 64 GB; storage: ultra-high I/O, 120 GB) on June 1, 2025. The instance price was $19,752 USD/month. On June 15, 2025, you deleted a CN from the instance, which was priced at $1,640 USD/month. Price difference = Fee of the deleted CN x Remaining period The remaining period in the formula is the number of remaining days in each calendar month divided by the maximum number of days in the calendar month. In this example, the remaining period and price difference are calculated as follows: Remaining period = 15 (Remaining days in June)/30 (Maximum number of days in June) = 0.5 Price difference = 1640 x 0.5 = $820 USD
Pay-per-use	Deleted CNs are no longer billed.

Billing Mode

Impact on Fees

Yearly/Monthly

After a CN is deleted, the system will stop charging you for it in the original subscription period.

GaussDB refunds the difference in price based on the remaining period.

Example (The prices below are for reference only. The actual prices are displayed on the console.)

Suppose you purchased a one-month, enterprise-edition distributed instance of V2.0-8.210 (configurations: 3 shards, 3 replicas, 3 CNs; instance specifications: dedicated, 8 vCPUs | 64 GB; storage: ultra-high I/O, 120 GB) on June 1, 2025. The instance price was $19,752 USD/month.

On June 15, 2025, you deleted a CN from the instance, which was priced at $1,640 USD/month.

Price difference = Fee of the deleted CN x Remaining period

The remaining period in the formula is the number of remaining days in each calendar month divided by the maximum number of days in the calendar month.

In this example, the remaining period and price difference are calculated as follows:

Remaining period = 15 (Remaining days in June)/30 (Maximum number of days in June) = 0.5
Price difference = 1640 x 0.5 = $820 USD

Pay-per-use

Deleted CNs are no longer billed.

Procedure

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > GaussDB.
On the Instances page, click the name of the instance for which you want to delete CNs.
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.
5. Check the result.
  On the Instances page, check that the instance is in the Deleting coordinator nodes state during the scale-in. After the instance status changes to Available, click the instance name. On the Basic Information page, check that the number of CNs matches the required quantity.