Tom Gundersen 626530818d worker/server: requeue unresponsive jobs ... If a job is unresponsive the worker has most likely crashed or been shut down and the in-progress job been lost. Instead of failing these jobs, requeue them up to two times. Once a job is lost a third time it fails. This avoids infinite loops. This is implemented by extending FinishJob to RequeuOrFinish job. It takes a max number of requeues as an argument, and if that is 0, it has the same behavior as FinishJob used to have. If the maximum number of requeues has not yet been reached, then the running job is returned to pending state to be picked up again.		2022-11-02 15:26:00 +01:00
..
fsjobqueue.go	worker/server: requeue unresponsive jobs	2022-11-02 15:26:00 +01:00
fsjobqueue_test.go	jobqueue: Move jobqueue out of internal	2022-07-04 15:37:28 +02:00