The lifecycle of a Lighthouse instance refers to the instance states that the instance goes through from its launch to its release.
Instance Statuses
The possible states during an instance's lifecycle are shown in the following table.
|
Creating | PENDING | Intermediate status | The status after the instance is created and before it goes to Running. |
Running | RUNNING | Steady status | The instance is in the normal running state. You can run your services on the instance in this state. |
Restarting | REBOOTING | Intermediate status | The instance enters the status before it goes to Running after being restarted by the console or through the API. If this status is maintained for a long time, an exception may occur. |
Starting | STARTING | Intermediate status | The instance enters the status before it goes to Running after being started by the console or through the API. If this status is maintained for a long time, an exception may occur. |
Shutting down | STOPPING | Intermediate status | The instance enters the status before it is shut down after being shut down by the console or through the API. If this status is maintained for a long time, it indicates an exception. Forced shutdown is not recommended. |
Shutdown | STOPPED | Steady status | The instance is stopped normally. An instance in a shutdown status cannot provide services. Some attributes of the instance can only be modified when the system is shut down. |
Terminating | TERMINATING | Intermediate status | The instance has not been terminated 7 days after its expiration or after the user actively performs the termination. |
Pending recycle | SHUTDOWN | Steady status | The instance is in the "To Be Recycled" status within 7 days after its expiration. This status does not provide services. |
Released | - | Steady status | The release operation is completed. The instance does not exist, services are unavailable, and the data is completely cleared. |
Special Instance States:
|
Freezing | FREEZING | The instance is frozen due to a violation. An instance in this status cannot access the private network or the public network, and cannot be operated. Go to Inbox to view details and handling methods. |
Restricting | NETWORK_RESTRICT | The instance is banned due to a violation. An instance in this status cannot access the private network or the public network. Go to Inbox to view details and handling methods. |
Instance Management Operations
Starting an Instance
After you select an instance plan on the purchase page, an instance is created based on the hardware configuration you selected, and the instance enters the Creating state. After an instance is created, it enters the Running state. A running instance has its connection and access services enabled. You can log in to the instance and perform related operations. For instructions, see Connect to a Linux Instance or Connect to a Windows Instance based on the instance's operating system. Restarting an Instance
We recommend that you restart the instance through the Tencent Cloud console or TencentCloud API, rather than running an operating system reboot command within the instance.
After you restart an instance, the instance enters the Restarting state.
Restarting an instance is equivalent to restarting a computer. After the restart, the instance retains its public/private IP addresses and all data on its hard disk.
Restarting an instance usually takes from tens of seconds to several minutes, depending on the instance configuration.
Shutting Down Instance
You can shut down an instance through the Tencent Cloud console, TencentCloud API, or other methods.
Shutting down an instance is equivalent to turning off your computer.
After an instance is shut down, its services are no longer available externally.
An instance being shut down is still displayed in the console.
Shutting down the instance is a prerequisite for certain configuration operations, such as adjusting hardware configurations or resetting passwords.
The shutdown operation itself does not change the public/private IP addresses of the CVM or any data on its hard disk.
Returning and Terminating an Instance
When you no longer need an instance, you can return and terminate it through the Tencent Cloud console or TencentCloud API.
Manual Termination/Return: For instances that have not expired, you can manually terminate or return them. After an instance is returned, it enters the Pending Recycle state.
Automatic Termination upon Expiration/Overdue Payment: If your instance is not renewed before its expiration date (including the expiration date itself), the system will suspend its service approximately 48 hours after expiration (the instance is shut down and disconnected, with only data retained). After service suspension, the instance enters the Pending Recycle state.
If an instance is not renewed within 15 days (including the 15th day) after the instance enters the Pending Recycle state, the system will release the instance approximately within 24 hours after the instance has been in the Pending Recycle state for 15 days. After release, the data in the instance will be cleared and cannot be recovered. For more information about terminating instances, see Return/Terminate an Instance.