QWQyyy commented on issue #5410:
URL: https://github.com/apache/openwhisk/issues/5410#issuecomment-1545095211

   On the whole, most hot starts are successful, but a small number of 
continuous internal errors:
   
![image](https://github.com/apache/openwhisk/assets/54056797/369bffe9-d874-4c63-a46a-0605046a03c9)
   It seems that the container failed to start or the scheduling failed. I seem 
to have disabled the activation log:
   
![image](https://github.com/apache/openwhisk/assets/54056797/e3c85665-8743-497e-9041-0492ec47f7ac)
   I use kubectl to check the pod's log, and it turns out that the node is 
overwhelmed, but in fact, I set the kubelet to have 400 pods per node, but the 
scheduling still cannot be completed.
   
![image](https://github.com/apache/openwhisk/assets/54056797/ca6f0af0-17d4-420c-a2c7-052fe4b8c011)
   
![image](https://github.com/apache/openwhisk/assets/54056797/69d2d722-fdec-4ec4-bddc-0f62e34eaf43)
   errors message is `Pod event for failed pod 
'wskowdev-invoker-00-1481-prewarm-nodejs16' null: 0/3 nodes are available: 1 
node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't 
tolerate, 2 Too many pods.`、`Pod event for failed pod 
'wskowdev-invoker-00-1484-prewarm-nodejs16' null: Successfully assigned 
openwhisk/wskowdev-invoker-00-1484-prewarm-nodejs16 to work2` and `failed 
starting prewarm, removed`
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to