Replies: 1 comment
-
It appears that the timeout is reliant on the system clock (time.time()). Therefore, this addresses the concern I initially raised in my question. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have a Flask/Gunicorn application with an API endpoint that allows users to change the system date and time via an API request. However, I've noticed that sometimes using this API endpoint leads to a "WORKER TIMEOUT" error. Could the act of changing the system date and time potentially impact Gunicorn's behavior, causing these timeouts?
Here are the relevant log entries for context:
In this scenario, my concern is whether altering the system date and time could have a bearing on Gunicorn's operation, potentially causing worker timeouts like the one observed. I understand that Gunicorn, along with many other applications, relies on accurate system time for various tasks. Could changing the system time abruptly lead to worker timeouts due to disrupted timing and interactions?
Thank you for your insights.
Beta Was this translation helpful? Give feedback.
All reactions