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
This timeout is specifically when gunicorn kills the worker because it was taking too long to respond. Maybe a busy loop or something like that. So this goes unnoticed.
It seems to only be in the backups API endpoint and one other response - so it's possible that these requests are just taking longer to fulfill.
A temporary fix is to increase the worker timeout to say 60 seconds instead of 30. Gunicorn seems to discourage this though.
Generally set to thirty seconds. Only set this noticeably higher if you’re sure of the repercussions for sync workers. For the non sync workers it just means that the worker process is still communicating and is not tied to the length of time required to handle a single request.
The text was updated successfully, but these errors were encountered:
API requests to
/backups
occasionally (9 times in the past 6 days) sometimes result in a gunicorn worker timing out.getsentry/raven-python#675
It seems to only be in the backups API endpoint and one other response - so it's possible that these requests are just taking longer to fulfill.
A temporary fix is to increase the worker timeout to say 60 seconds instead of 30. Gunicorn seems to discourage this though.
The text was updated successfully, but these errors were encountered: