Re: [I] How to correctly modify OpenWhisk’s gateway blocking limit from source code (currently 60s) [openwhisk]

["style95 (via GitHub)" <gi...@apache.org>]

style95 commented on issue #5467:
URL: https://github.com/apache/openwhisk/issues/5467#issuecomment-1975057329

   @QWQyyy 
   First, IIRC, the timeout of the Kubernetes client in the above log is related to the pod creation.
   It's not related to the execution of an activation.
   The action timeout controls the execution timeout against the pod(container).
   https://github.com/apache/openwhisk/blob/5529cc49d31f135dfdac4f2a2072ca46bfd754de/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala#L834
   
   I think you need to ensure you can invoke your action successfully with the `wsk action invoke` command.
   If you can successfully invoke your action without the API gateway, then the culprit is the API gateway.
   If your action is invoked well but it is changed to the asynchronous(get 202 response) at some point, it's related to the controller configuration. If you can't even invoke your activation in the asynchronous mode as well, you may not configure the action timeout properly.
   


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org