Instance Lifecycle
Last updated：2024-09-11 10:44:32
Instance Lifecycle
The lifecycle of a cloud server instance covers the entire process from creation (purchase) to deletion (termination). Reasonable planning and management of instance lifecycles can ensure that applications running on the instance can be efficiently, conveniently, and economically provided as services to customers. Instance states can be divided into intermediate states and stable states. If the instance remains in an intermediate state for a long time, it indicates that the instance has encountered an exception.
Instance State
In a lifecycle, an instance has several fixed states, as shown in the table below:
| Status Name | Status Attribute | Status Description |
|---|---|---|
| Creating | Intermediate state | The instance is being created and is in the state before it enters the "Running" state. |
| Running | Stable state | The instance is running normally and can run business on it. |
| Rebooting | Intermediate state | The instance is rebooting after control panel or API operation and is in the state before it enters the "Running" state. If it remains in this state for a long time, it may have encountered an exception. |
| Resetting | Intermediate state | The instance is resetting its operating system or disk after control panel or API operation, and is in the state before it enters the "Running" state. |
| Shutting down | Intermediate state | The instance is being shut down after control panel or API operation, and is in the state before it enters the "Stopped" state. If it remains in this state for a long time, it may have encountered an exception. |
| Stopped | Stable state | The instance has been successfully stopped, and cannot provide services externally in this status. Some properties can only be modified in this state. |
| Destroying | Intermediate state | The instance is being deleted because it has expired, the account is in arrears, or the user initiates the deletion operation, and the deletion is not yet complete. |
| To be Recovered | Stable state | The instance has been deleted within 24 hours passively, or within 2 hours initiated by the user, and is in the "to be recovered" state. It cannot provide external services in this status. |
| Released | Stable state | When the release operation is completed, the original instance will no longer exist, and cannot provide services anymore, and the data will be completely erased. |
| Updating | Intermediate state | The instance is being migrated, deployed, modified specifications or other maintenance operations, If it remains in this state for a long time, it may have encountered an exception. |
| Error | Stable state | The instance is in a fault or other unknown state. In this state, the instance cannot provide normal business services. Please submit a ticket for support. |
Creating instance
- After executing the create operation, the instance will enter the "Creating" status. The cloud server will be created according to the specified instance specifications and image.
- After the instance is successfully created, it will enter the "Running" status and provide normal connection and access services to the user.
For more information about instance creation, please see Purchase instance.
Stopping instance
- After executing the shut down operation, the instance will enter the "Shutting down" status.
- Shutting down the instance is equivalent to shutting down the cloud server. The stopped instance will still be displayed on the control panel.
- Stopped instances no longer provide services externally, but will still be charged normally.
- Shutting down the instance itself does not change the public IP address, private IP address, or all data on its hard disk.
- Stopping the instance is a prerequisite for some configuration operations, such as binding key pairs, reinstalling the system, etc.
For more information about stopping instances, please see Stopping instances.
Starting instance
- After executing the start operation, the instance will enter the "Starting up" status.
- Starting the instance usually takes several seconds to several minutes, depending on the configuration of the instance.
For more information about starting instances, please see Starting instances.
Rebooting instance
We recommend that users use the control panel or API to restart the instance rather than running the operating system restart command within the instance.
- After executing the reboot operation, the instance will enter the "Rebooting" status.
- Rebooting the instance is equivalent to restarting the cloud server. After the restart, the instance still retains its public IP address, private IP address, and all data on its hard disk.
- Rebooting the instance usually takes several seconds to several minutes, depending on the configuration of the instance.
For more information about rebooting instances, please see Rebooting instances.
Instance expiration
- After the instance expires or the account is overdue, it will be moved to the recycle bin, and will be permanently released after being kept in the recycle bin for up to 24 hours.
- Once an instance is in the recycle bin, it will be automatically released if the reservation period is not restored. Please perform the restoration or release operation within the specified time to avoid any loss.
For more information about instance billing, please see Product billing.
Destroy/Return instance
- After executing the "Destroy/Return" operation, the instance will be moved to the recycle bin.
- Active destruction: for non-expired pay-as-you-go instances or non-default pay-monthly instances, users can manually delete resources. This type of instance will be permanently released after being kept in the recycle bin for up to 2 hours.
- Passive destruction: After the instance expires or the account is overdue, users can choose to restore or release the resources. This type of instance will be permanently released after being kept in the recycle bin for up to 24 hours.
For more information about destroying/returning instances, please see Destroy/Return instance,Recycle or restore instance.