You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: