We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Moving discussion from Ouranosinc/raven#391 to here.
Long requests cause timeouts in the current configuration of finch using gunicorn.
gunicorn
According to the doc (https://docs.gunicorn.org/en/latest/design.html#choosing-a-worker-type), we shouldn't be using the sync workers for "Applications making long blocking calls (Ie, external web services)", which is exactly was finch is all about.
sync
2 solutions tried (in the gunicorn command) and resolved the timeout problem :
-t 0
-k gthread
AFAIU, the timeout is still counted for async worker, but only if they are idle.
I'm not sure of the implication of either solutions.
The text was updated successfully, but these errors were encountered:
@cjauvin Possibly relevant to your current analysis.
Sorry, something went wrong.
No branches or pull requests
Moving discussion from Ouranosinc/raven#391 to here.
Long requests cause timeouts in the current configuration of finch using
gunicorn
.According to the doc (https://docs.gunicorn.org/en/latest/design.html#choosing-a-worker-type), we shouldn't be using the
sync
workers for "Applications making long blocking calls (Ie, external web services)", which is exactly was finch is all about.2 solutions tried (in the gunicorn command) and resolved the timeout problem :
-t 0
to disable timeouts entirely.-k gthread
to use an asynchronous worker.AFAIU, the timeout is still counted for async worker, but only if they are idle.
I'm not sure of the implication of either solutions.
The text was updated successfully, but these errors were encountered: