Nginx Ingress To Not Timeout when backend takes time to respond #12019
Labels
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
triage/needs-information
Indicates an issue needs more information in order to work on it.
What happened:
Hey there,
When using Nginx Ingress in GCP, I'm experiencing a timeout issue with long response times, causing a 504 gateway timeout on the client side. I think NGINX using default 60 seconds timeout.
Error on the client side: 504 Gateway Timeout
What you expected to happen:
We want to set the timeout to 90 seconds and let NGINX not re try when backend takes longer duration.
Lets say backend takes more than 90 seconds, let NGINX not retry as backend may be down.
So we don't want NGINX to retry again instead return 504.
Is there a config to let Ingress-Nginx know to retry in specific use cases and not to re try in specific use cases.
NGINX retries for 3 times to backend. Which is causing additional request's.
We know the backend is down and not able to responsd. We don't want additional request's to backend.
The text was updated successfully, but these errors were encountered: