You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+1 I am running into this same issue. The synthetics worker is unable to schedule the minion job pod for the health checks due to the problem with not having enough CPU.
In the first startup, there is a pod, the is spawned in the same namespace called
synthetic-healthcheck-xxxx
or something similar.Then at one point, this job/pod is using more than 3500m, going out of CPU.
Moreover, for some reason, I've got 79509 folders:
Why does the synthetic-healthcheck require so much CPU?
The text was updated successfully, but these errors were encountered: