Repository navigation
Keep database connection alive in job runner wait loop #246
Description
The main loop of the job runner waits for NOTIFY events via a select() call, with a 60 seconds timeout.
If there are no activity in the queue_job table it seems that tcp keepalives are not sent (in that very specific scenario), causing some intermediaries (such as haproxy) to close the connection, making the jobrunner to restart on a socket error, in turn triggering #245.
A solution (to be tested) is to insert a conn.execute("SELECT 1") around here.
Activity
[IMP] - keep connexion alive in case of job inactivity
houzefa-abba commentedon Aug 7, 2020
Another take on this we didn't get around to submit here as the solution is Linux-specific and not optional: xcgd#1
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity
[IMP] - keep connexion alive in case of job inactivity