Help Center/ Cloud Container Engine/ User Guide (Ankara Region)/ FAQs/ Node/ Specification Change/ What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?
Updated on 2024-12-04 GMT+08:00
View PDF
Share

What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?

Context

The kubelet option cpu-manager-policy defaults to static, allowing pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. If you modify CCE node specifications on the ECS console, the original CPU information does not match the new CPU information. As a result, workloads on the node cannot be restarted or created.

For more information, see Control CPU Management Policies on the Node.

Impact

The clusters that have enabled a CPU management policy will be affected.

Solution

  1. Log in to the CCE node (ECS) and delete the cpu_manager_state file.

    Example command for the file deletion: 
    rm -rf /mnt/paas/kubernetes/kubelet/cpu_manager_state

  2. Restart the node or kubelet. The following is the kubelet restart command: 

    systemctl restart kubelet

  3. Verify that workloads on the node can be successfully restarted or created.
Parent topic: Specification Change