Closed kmala closed 8 years ago
I've seen the exact same behaviour yesterday but scaling the replicas number to 0 and then back to 1 on the deis-builder's RC corrected that.
Before doing the scaling stuff described above I checked the running processes with a "ps faux" and I noticed that a defunct child process linked to boot was consuming a lot of CPU. Have you got the same ?
EDIT : Here are the defunct child processes I've seen but, my bad, they cannot consume CPU by nature and they are probably a kind of trace from a failed push I think.
root 12342 92.9 0.2 23052 18956 ? Ssl Mar30 1921:16 \_ boot server
root 25779 0.0 0.0 0 0 ? Z Mar30 0:00 \_ [pre-receive] <defunct>
root 26513 0.0 0.0 0 0 ? Z Mar30 0:00 \_ [pre-receive] <defunct>
I'm seeing 100% CPU on deis-builder with a new install of beta3 that starts spontaneously and continues indefinitely.
Can you try the beta4 because the issue was completely fixed in beta4 and exists in beta3
will do. thanks.
Builder using high CPU on GKE clusters. Replication: Depoly a wokrlfow-dev or workflow-beta1 charts and do a docker stats on the builder container:
top on the node gives