Stopping a GaussDB Node

Scenarios

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

Constraints

• Stopping a node may expose the instance to higher risk of downtime. Exercise caution when performing this operation.
• The following operations cannot be performed when a node is being stopped: changing specifications, backing up data, resetting passwords, rebooting an instance, and deleting an instance. When you perform these operations, nodes cannot be stopped.
• HA monitoring will be disabled for a node before it is stopped. HA monitoring will be enabled when you start the node. You can also manually enable HA monitoring for a node. After HA monitoring is disabled, the node status will not be monitored.
• If a stopped node contains at least half of the replicas of the corresponding DN shard, the instance may be abnormal and a single node may fail to be started.
• After a node is stopped, you can still log in to the node using CLI commands, but all database-related operations cannot be performed.
• For a distributed instance, at least one CN in the instance must be available, or the entire instance will be unavailable.
• Instance parameters cannot be modified if there are stopped nodes in an instance.
• If a node is stopped for too long, an alarm is triggered. You can start the node to rectify the fault and clear the alarm.

Billing

For nodes of pay-per-use instances, billing for the VM hosting it stops when the node is stopped, but billing continues for associated resources like EIPs, storage, and backups. For nodes of yearly/monthly instances, all related resources are billed even after the node 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 the name of the target instance to go to the Basic Information page.
5. In the Node List area, click Stop in the Operation column.
6. In the Stop Node dialog box, enter YES, and click OK.
   Figure 1 Stopping a node
   

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