Actions
Story #8291
closed
As a user, I can configure WORKER_TTL
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 91
Quarter:
Description
Currently the worker timeout is hard coded to 30 seconds. In environments where volume backing Postgresql has its I/O saturated, it's been observed that even an idle system can have its workers timeout.
Solution¶
Move the WORKER_TTL setting to settings.py and document it. It will default to 30 seconds, which is the same value it is today.
Actions
.
Turn WORKER_TTL into a setting
The heartbeat rate will scale proportional to that timeout.
fixes #8291
Co-authored-by: bmbouter bmbouter@gmail.com