-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Configurable api server timeout on embedded nginx #24471
feat: Configurable api server timeout on embedded nginx #24471
Conversation
/build-deploy-preview skipTests=true |
Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/5270272390. |
Deploy-Preview-URL: https://ce-24471.dp.appsmith.com |
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/5333899127. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/5333899127.
To know the list of identified flaky tests - Refer here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to confirm if a long-running API call can be made in the DP, but the DP seems to be down. Can you check please? Can you also review the below and share you thoughts?
From http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout
The timeout is set only between two successive read operations, not for the transmission of the whole response.
So, the effective timeout from setting this can be much longer. Is this what we're expecting here?
From http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_connect_timeout,
[...] timeout for establishing a connection with a proxied server.
This is the time for just establishing the connection, and shouldn't affect timeouts from long-running queries, right?
From http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_send_timeout,
[...] timeout for transmitting a request to the proxied server.
This is timeout between adjacent bytes of data sent to the backend. This is also not what we want here, right?
Also, the default value for all three from docs is shown as 60s
, not 60
. Does it work without the s
as well?
@sharat87 The configs work without specifying seconds.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and works. Made suggestions for some whitespace cleanup, but otherwise ready to merge.
Co-authored-by: Shrikant Sharat Kandula <shrikant@appsmith.com>
Co-authored-by: Shrikant Sharat Kandula <shrikant@appsmith.com>
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/5444864297. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/5444864297.
To know the list of identified flaky tests - Refer here |
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/5450871447. |
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/5450871447. |
@sum35h Thanks for this fix! |
@shalomy-cyera For the helm deployment, we'll need to apply the same settings to the ingress controller. We will update you once we publish the docs to apply the setting to helm installations. |
Thanks a lot @sum35h ! |
You need to add configuration settings to the UI |
Description
APPSMITH_SERVER_TIMEOUT
Testing
How Has This Been Tested?