Stopping a GaussDB Instance

Scenarios

You can manually stop a GaussDB instance. This operation stops the component processes on all nodes of the instance, but does not stop the VM or physical server.

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.
• After the instance is stopped, all resources will continue to be billed.

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.