What Should I Do If Residual Process Resources Exist Due to an Earlier npd Add-on Version?
Problem Description
When the node load is heavy, residual npd process resources may exist.
Symptom
After successful login to the ECS node where the CCE cluster runs, it is found that there are a large number of npd processes exist.
Solution
Upgrade the npd add-on to the latest version.
- Log in to the CCE console and click the cluster. In the navigation pane, choose Add-ons. On the displayed page, click Upgrade under npd.
If the npd add-on version is 1.13.6 or later, you do not need to upgrade it.
- On the Specify Basic Information page, select the cluster and the add-on version (for example, 1.13.6), and click Next.
- Click Upgrade to upgrade the npd add-on. Note that the npd add-on has no configurable parameters and can be directly upgraded.
Chart and Add-on FAQs
- What Should I Do If the nginx-ingress Add-on Fails to Be Installed on a Cluster and Remains in the Creating State?
- What Should I Do If Residual Process Resources Exist Due to an Earlier npd Add-on Version?
- What Should I Do If a Chart Release Cannot Be Deleted Because the Chart Format Is Incorrect?
- Does CCE Support nginx-ingress?
- Why Does Add-on Installation Fail and Prompt "The release name is already exist"?
- What Should I Do If a Release Creation or Upgrade Fails and "rendered manifests contain a resource that already exists" Is Displayed?
- What Should I Do If a kube-prometheus-stack Pod Fails to Be Scheduled and the Message "node(s) had volume node affinity conflict" Is Displayed?
- What Should I Do If a Chart Fails to Be Uploaded?
- How Do I Configure the Add-on Resource Quotas Based on Cluster Scale?
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.
Chatbotmore