Deleting a Cluster
Scenario
- You can directly delete pay-per-use clusters. For details, see Deleting a Pay-per-Use Cluster.
- Yearly/Monthly clusters cannot be deleted directly. Unsubscribe from clusters that have not expired or release clusters that have expired and have not been renewed. For details, see Unsubscribing from or Releasing a Yearly/Monthly Cluster.
Precautions
- Deleting a cluster will not delete the yearly/monthly-billed resources in the cluster, and their billing continues.
- Deleting a cluster will delete the workloads and Services in the cluster, and the deleted data cannot be recovered. Before performing this operation, ensure that related data has been backed up or migrated.
- If you choose to delete a cluster with the nodes in it, the system disks and data disks attached to the nodes will also be deleted. Back up data before the deletion.
- If you delete a cluster that is not running (for example, frozen or unavailable), associated resources, such as storage and networking resources, will remain.
- A hibernated cluster can be deleted only after it is awakened.
Billing
Billing for a cluster stops once it is deleted. However, residual resources in the cluster, such as yearly/monthly-billed resources, will still incur charges.
Deleting a Pay-per-Use Cluster
- Log in to the CCE console. In the navigation pane, choose Clusters.
- In the cluster list on the right, locate the cluster to be deleted and click
. In the drop-down list, choose Delete.
Figure 1 Deleting a cluster - In the displayed Delete Cluster dialog box, select the resources to be released.
- When you delete a node from a cluster, the following options are available:
- Retain: The node as well as the data on the system disk and data disks will be retained.
- Delete: The node will be deleted with the cluster. This option is unavailable for yearly/monthly-billed nodes. To delete such nodes, manually unsubscribe from them.
- Reset: The node will be retained and reset. The data on the system disk and data disks will not be retained.
- Delete cloud storage resources associated with workloads in the cluster.
When deleting underlying cloud storage resources bound to storage volumes in a cluster, pay attention to following constraints:
- The underlying storage resources are deleted according to the reclamation policy you defined for the storage volumes. For example, if the reclamation policy of storage volumes is Retain, the underlying storage resources will be retained after the cluster is deleted.
- If there are more than 1000 files in the OBS bucket, manually clear the files and then delete the cluster.
If the storage volume's reclamation policy is set to Retain, the following table lists the method of deleting PVs based on their type.PV Type
Associated Underlying Storage
Whether to Delete Underlying Storage
EVS
Disks
Yes
DSS
Disks
Yes
SFS
SFS Capacity-Oriented or general purpose file system (SFS 3.0 Capacity-Oriented)
Yes
OBS
OBS buckets or parallel file systems
Yes
SFS Turbo
SFS Turbo file systems
Yes
Local PV
Logical volumes mounted to the node
Determined based on the policy selected when the cluster is deleted.
If you choose to retain the node, the logical volumes will not be deleted. If you choose to delete or reset the node, the logical volumes will be deleted.
General purpose file system (SFS 3.0 Capacity-Oriented) subdirectory
A directory in general purpose file system (SFS 3.0 Capacity-Oriented)
No
SFS Turbo subdirectory
A directory in SFS Turbo
No
- Delete network resources such as load balancers in a cluster. (Only automatically created load balancers will be deleted).
- Delete all log groups, including their log streams, for the cluster in LTS. If you do not select this option, the LTS logs will not be deleted, and you will be billed for them. For details, see Price Calculator.
- When you delete a node from a cluster, the following options are available:
- Enter DELETE and click Yes to start deleting the cluster.
The delete operation takes 1 to 3 minutes to complete. If the cluster is removed from the cluster list, the cluster has been deleted.
Unsubscribing from or Releasing a Yearly/Monthly Cluster

- When you unsubscribe from or release a cluster, only the resources associated with the order are unsubscribed from. Non-associated resources are retained and their billing keeps going.
- Yearly/Monthly-billed clusters will be automatically released after their retention period expires. If the nodes in the cluster expire, they will also be released. If the nodes have not expired, CCE will not perform any operations on them. Their related data will be retained, and billing for the resources will continue. Monitor your account for expired clusters and renew them promptly to prevent data loss from node reinstallation.
- If an order contains resources in a primary-secondary relationship, unsubscribe from the resources separately.
- Unsubscribe from resources. For details, see Unsubscription Rules.
- If you are unsubscribing from a resource that is being used, review the resource information and refund information carefully. The resource cannot be restored after unsubscription. You can unsubscribe from a renewal period that has not yet taken effect for your renewed resources on the Unsubscribe from Renewal Period page.
- Unsubscribing from a resource associated with other yearly/monthly-billed resources may affect the normal use of those resources.
Unsubscribing from a resource associated with other pay-per-use resources will not affect the normal use of those resources. They will be billed normally.
- Log in to the CCE console. In the navigation pane, choose Clusters.
- Locate the cluster to be unsubscribed from, click ... to view more operations on the cluster, and choose Unsubscribe or Release.
Figure 2 Unsubscribing from a cluster
- On the displayed page, select the resources to be released.
- When you delete a node from a cluster, the following options are available:
- Retain: The node as well as the data on the system disk and data disks will be retained.
- Delete: The node will be deleted with the cluster. This option is unavailable for yearly/monthly-billed nodes. To delete such nodes, manually unsubscribe from them.
- Reset: The node will be retained and reset. The data on the system disk and data disks will not be retained.
- Delete cloud storage resources associated with workloads in the cluster.
When deleting underlying cloud storage resources bound to storage volumes in a cluster, pay attention to following constraints:
- The underlying storage resources are deleted according to the reclamation policy you defined for the storage volumes. For example, if the reclamation policy of storage volumes is Retain, the underlying storage resources will be retained after the cluster is deleted.
- If there are more than 1000 files in the OBS bucket, manually clear the files and then delete the cluster.
If the storage volume's reclamation policy is set to Retain, the following table lists the method of deleting PVs based on their type.PV Type
Associated Underlying Storage
Whether to Delete Underlying Storage
EVS
Disks
Yes
DSS
Disks
Yes
SFS
SFS Capacity-Oriented or general purpose file system (SFS 3.0 Capacity-Oriented)
Yes
OBS
OBS buckets or parallel file systems
Yes
SFS Turbo
SFS Turbo file systems
Yes
Local PV
Logical volumes mounted to the node
Determined based on the policy selected when the cluster is deleted.
If you choose to retain the node, the logical volumes will not be deleted. If you choose to delete or reset the node, the logical volumes will be deleted.
General purpose file system (SFS 3.0 Capacity-Oriented) subdirectory
A directory in general purpose file system (SFS 3.0 Capacity-Oriented)
No
SFS Turbo subdirectory
A directory in SFS Turbo
No
- Delete network resources such as load balancers in a cluster. (Only automatically created load balancers will be deleted).
- Delete all log groups, including their log streams, for the cluster in LTS. If you do not select this option, the LTS logs will not be deleted, and you will be billed for them. For details, see Price Calculator.
- When you delete a node from a cluster, the following options are available:
- Click Yes. The unsubscription or release takes 1 to 3 minutes to complete. If the cluster is removed from the cluster list, the cluster has been unsubscribed.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot