How to correctly modify OpenWhisk’s gateway blocking limit from source code (currently 60s) about openwhisk

[QWQyyy]

@style95 Could you please give me some guidance?

[style95]

It seems you are using the API gateway, could you check again without the API gateway first?

[QWQyyy]

It seems you are using the API gateway, could you check again without the API gateway first?

[style95]

You are supposed to be able to invoke the action with wsk.
I think that's the starting point to look into.

[QWQyyy]

You are supposed to be able to invoke the action with wsk. I think that's the starting point to look into.

I'm sure that my gateway can correctly ensure that the end-to-end response is greater than 60 seconds. I have also explicitly configured the controller. I can't seem to find any more places where I need to configure the timeout. Can you give me some suggestions?

[QWQyyy]

wsk does work, but only the information recorded by the activation can be viewed. We prefer to complete our services directly through the gateway HTTP request.

[QWQyyy]

[QWQyyy]

It seems that I should also pay attention to apigateway:

[QWQyyy]

At the same time, how should I correctly configure the execution time limit? What I wrote in value.yaml is 500 minutes, but when I use wsk to set the upper limit of execution time of 500 minutes, the invoker log prints 600s?

[QWQyyy]

I am currently studying the source code of openwhisk in depth, and I hope to make some solid changes.

[style95]

@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).

openwhisk/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala

Line 834 in 5529cc4

actionTimeout,

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.

[QWQyyy]

@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).

openwhisk/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala

Line 834 in 5529cc4

actionTimeout,

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.

Okay let's try it!

[QWQyyy]

@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).

openwhisk/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala

Line 834 in 5529cc4

actionTimeout,

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.

It is true that I can successfully access my functions using wsk, but it is only limited to functions within 60 seconds. For functions that take longer to execute, the wsk client also returns an Oops--504 error, but I found through the resource manager htop that the function code is still During execution, after the function is executed, you can see from wsk activation that the function ends correctly. This confuses me.