Scenarios
If you need to stop the instance service or need to perform a configuration that can only be modified when the instance is shut down, you can shut down the instance. Shutting down an instance is equivalent to shutting down the local computer.
Must-Knows
- You can use system commands to shut down the instance (such as the shutdown command in Windows and the shutdown command in Linux), or you can use the Converge Cloud console to shut down the instance. It is recommended to open the console during shutdown to view the shutdown process to see if there is any problem.
- After the instance is shut down, services will not be available. Therefore, before the shutdown, ensure that the Cloud Virtual Machine has suspended business requests.
- The instance is shut down normally. The status changes to Shutting Down first, and then changes to Shutdown after the shutdown is complete. If the shutdown time is too long, problems may occur. For details, see Shutdown Related to avoid forced shutdown.
- After the instance is shut down, all storage remains connected to the instance and all disk data is preserved. Data in memory will be lost.
- Shutting down an instance does not change the physical characteristics of the instance. The public network IP and private network IP of the instance remain unchanged; Elastic IP maintains the binding relationship, but due to the service interruption, you will get an error response when accessing these IPs.
- If the shutdown instance belongs to the backend server cluster of the Cloud Load Balancer instance, after shutdown, services will not be available.
- If a health check policy is configured, the shutdown instance can be automatically masked and no requests will be forwarded to it. If no health check policy is configured, the client may receive a 502 error response. For more information, see Health Check.
- If the shutdown instance is in Auto Scaling Group, the Auto Scaling service will mark the shutdown instance as poor health, may remove it from the auto scaling group, and launch a replacement instance. For more information, see Auto Scaling.
Operation Steps
Shut down instance via console
- Log in to the CVM console.
- Select different operation modes according to actual needs.
- Shut down a single instance: Select the instance that needs to be shut down, and in the action bar on the right, choose More > CVM Status > Shut Down.
- Shut down multiple instances: Select all instances you want to shut down and click Shutdown at the top of the list to shut them down in batch.
Instances that cannot be shut down will display the reason.Note:If a manual forced shutdown command is issued, the forced shutdown action will be performed first.
Shut down the Instance via API
Refer to API Documentation > StopInstances API.
Subsequent Operations
You can modify the following instance attributes only when the instance is shut down:
- Instance configuration (CPU, memory): To change the instance type, see Adjusting Instance Configuration.
- The size of the mounted Cloud Block Storage: To adjust the size of the Cloud Block Storage, see Scale-out Cloud Block Storage.
- Change password: Refer to Log-in Password.
- Load key: Refer to SSH Keys.