Skip to content
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

TIMEOUT parameter not working #132

Open
pererumbo opened this issue Nov 25, 2021 · 1 comment
Open

TIMEOUT parameter not working #132

pererumbo opened this issue Nov 25, 2021 · 1 comment

Comments

@pererumbo
Copy link

I'm running the docker on an AWS instance and I have an endpoint that performs heavy calculations. Depending on the input it can take more than 1 minute to process. The problem is that for big inputs it always returns a 504 Gateway Timeout after 60 seconds.

I've tried to set the TIMEOUT parameter in the docker run command as specified in the docs but it doesn't seem to modify this timeout. I've checked the gunicorn documentation and it says that the default timeout is 30 seconds and the grace_timeout is also 30 seconds. This make me think that these parameters are not being overwritten because the sum of both is 60 seconds, exactly the same time it takes to raise the timeout error.

@flyingjoe
Copy link

If you're using an ELB in front of your instance, it might be the Load Balancer closing the connection (default timeout is 60s)
https://aws.amazon.com/de/blogs/aws/elb-idle-timeout-control/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants