yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
a41a4e0331fbc0beff63bb28fa59228cc9a751df
doc-exports/docs/cce/umn/cce_faq_00130.html
qiujiandong1 ab1e53a279 CCE UMN 20251031 version 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2026-01-15 10:25:22 +00:00

2.2 KiB
Raw Blame History

What Should I Do If Residual Process Resources Exist Due to an Earlier CCE Node Problem Detector Add-on Version?

Description

When the node load is heavy, residual CCE Node Problem Detector 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 CCE Node Problem Detector processes exist.

Solution

Upgrade the CCE Node Problem Detector add-on to the latest version.

  1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons, locate the CCE Node Problem Detector add-on, and click Upgrade.

    If the CCE Node Problem Detector add-on version is 1.13.6 or later, you do not need to upgrade it.

  2. In the window that slides out from the right, configure the parameters and click OK.
Parent topic: Chart and Add-on