The lifecycle of a CDH refers to the statuses it goes through from startup to termination. Proper management of CDH instances from enabling to terminating ensures that applications running on instances can provide services efficiently and economically.
CDH Status
| Status Name | Status Attributes | Status Description |
|---|---|---|
| Creating | Intermediate State | After creation, it enters the status before it is running. |
| Running | Steady State | Normal running status, in which CVM instances can be allocated on CDH instances. |
| Recycled | Steady State | The CDH for monthly subscriptions will be placed in the Recycle Bin status within 7 days after its expiration date. This status is not available to external users. After renewal, the status will be restored to running. |
| Terminated | Steady State | Once the terminate operation is completed, the original CDH will no longer exist, be unable to provide services, and the data will be completely cleared. |
Status Transition Diagram
CDH Instance Recycling Mechanism
- If your CDH is not renewed before expiration (including the expiration day), the system will suspend its service at the expiration time. The host and all CVM instances on the host will be disconnected from the network and shut down, and the CBSs related to the instances will stop serving, but the data will be retained.
- From the day after expiration to 7 days after expiration, you can still renew and recover the CDH in the Recycle Bin.
If a renewal is made during the period, the instances on the CDH as well as their associated networks and CBS will be restored to availability. - If your host resources are not renewed after 7 days of expiration (including the 7th day), the system will start releasing the resources at 00:00 on the 8th day after expiration. All CVM instances on the CDH will be terminated, and the local disks, cloud disks, and data related to the instances will be cleared and cannot be recovered.