Page Comparison

Check node CPU and ssh to the node with high CPU to see which docker process is running high on CPU and delete the related ONAP deployment if

you don't need it for testing (e.g. dev-log and dev-pomba)

root@oom-rancher:~# kubectl -n onap top node
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY% 
oom-etcd-1 281m 14% 1593Mi 41% 
oom-etcd-2 318m 15% 1459Mi 37% 
oom-etcd-3 268m 13% 1479Mi 38% 
oom-k8s-01 845m 10% 13296Mi 83% 
oom-k8s-02 4162m 52% 12280Mi 77% 
oom-k8s-03 473m 5% 1321Mi 8% 
oom-k8s-04 1761m 22% 12395Mi 77% 
oom-k8s-05 7076m 88% 11676Mi 73% 
oom-k8s-06 7738m 96% 12022Mi 75% 
oom-k8s-07 1507m 18% 11035Mi 69% 
oom-k8s-08 5237m 65% 5155Mi 32% 
oom-k8s-09 849m 10% 10874Mi 68% 
oom-k8s-10 6467m 80% 9340Mi 58% 
oom-k8s-11 1408m 17% 10462Mi 65% 
oom-k8s-12 917m 11% 10062Mi 63% 
oom-orch-1 463m 23% 2896Mi 75% 
oom-orch-2 281m 14% 1259Mi 32%