Prevent "[CRITICAL] WORKER TIMEOUT" error message #3229
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
averikitsch
approved these changes
Mar 30, 2020
dinagraves
approved these changes
Mar 30, 2020
markhobson
added a commit
to acteng/update-your-capital-schemes
that referenced
this pull request
Oct 11, 2023
Prevents `[CRITICAL] WORKER TIMEOUT` log messages when Cloud Run takes resources away from Gunicorn. Recommended by: https://cloud.google.com/run/docs/tips/python#optimize_the_wsgi_server More info: GoogleCloudPlatform/python-docs-samples#3229
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a Cloud Run container instance idles between requests and withdraws CPU, there is a lack of heartbeat from the worker to the gunicorn arbiter process. A service in this state can have "WORKER TIMEOUT" error logs once CPU is restored upon receiving an HTTP request.
The timeout on workers is not an essential part of server resource management. Per benoitc/gunicorn#2291, gunicorn supports setting an unlimited timeout with
--timeout 0. Let's do that to clean up the logs.