Stopping a GaussDB Instance

Scenarios

You can manually stop a GaussDB instance. This operation terminates the database processes across all nodes within the instance and shuts down the VMs hosting the nodes. However, resources like EIPs, storage, and backups are retained. If you are using DB instances mainly for routine development, you can stop the pay-per-use instances during idle periods to cut down on costs.

Constraints

• The following operations cannot be performed when an instance is being stopped and after it is stopped: scaling up storage, changing specifications, backing up data, resetting passwords, rebooting the instance, and deleting the instance.
• After an instance is stopped, its component information cannot be queried.
• After an instance is stopped, it cannot provide services. Exercise caution when performing this operation.
• Instance parameters cannot be modified after an instance is stopped.
• Stopping an instance will stop all component processes in it and workloads will be interrupted. Exercise caution when performing this operation.

Billing

For pay-per-use instances, billing for the VMs hosting it stops when the instance is stopped, but billing continues for associated resources like EIPs, storage, and backups. For yearly/monthly instances, all related resources are billed even after the instance is stopped.

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 More in the Operation column of the target instance and choose Stop.
5. In the displayed dialog box, click OK.
   Figure 1 Stopping an instance
   

6. Refresh the instance list and view the status of the instance. If its status is Stopped, it has been stopped successfully.