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
@science695: Sorry for the delay, but thanks for the heads up! Yes, you're right that this was fixed earlier and is now part of the v0.15.1 release. This should now be configurable via /etc/api-umbrella/api-umbrella.yml with the following settings:
What's fixed in v0.15.1 is that configuring these nginx settings in API Umbrella should now automatically tune the underlying TrafficServer settings to match.
I have been trying to get an api long-running process (more than 15 minutes) to run through umbrella.
I have set all 3 nginx timeouts to 3600 seconds, but it keeps getting a gateway timeout at 900 (15minutes).
I found a setting in trafficserver/records.config:
It seems like this setting shold also be tied to proxy_read_timeout like
api-umbrella/src/api-umbrella/cli/read_config.lua
Line 370 in ae8ef41
Is there any danger of setting this in the api-umbrella.yml config file:
or setting it to 0 so it doesn't introduce another timeout to the process?
The text was updated successfully, but these errors were encountered: