Skip to content
This repository has been archived by the owner on Sep 21, 2018. It is now read-only.

Jobs can be in limbo after a worker failure #16

Open
BruceBGordon opened this issue Nov 6, 2015 · 1 comment
Open

Jobs can be in limbo after a worker failure #16

BruceBGordon opened this issue Nov 6, 2015 · 1 comment

Comments

@BruceBGordon
Copy link
Contributor

When a worker fails (cancelled for example), a job can be on stuck on the queue. A mildly effective fix would be for a worker at startup to see if any jobs are assigned to it and mark them as cancelled.

@thekushpatel
Copy link
Contributor

Agreed. So my idea for this was to have a Cleanup class that would have multiple functions including one that did exactly what you mentioned. Another function would be to remove files from the disk for jobs that no longer exist. These functions would be called on startup and could also be called on some schedule.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants