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
If a unique job is 'active' and the worker that is processing the job becomes unavailable and never calls done(), and doesn't respond to the ttl timeout, the job will be stuck in 'active', and therefore never gets re-scheduled due to:
I will submit a pull request to also check if the last_updated value is older than the job ttl and schedule the next job - this way they do not end up stale.
The only reservation I have about this method is that in a situation where the worker is just unable to talk to redis, it may complete the work twice.
The text was updated successfully, but these errors were encountered:
I believe this is due to a change I introduced:
If a unique job is 'active' and the worker that is processing the job becomes unavailable and never calls done(), and doesn't respond to the ttl timeout, the job will be stuck in 'active', and therefore never gets re-scheduled due to:
https://github.com/lykmapipo/kue-scheduler/blob/master/index.js#L56
I will submit a pull request to also check if the last_updated value is older than the job ttl and schedule the next job - this way they do not end up stale.
The only reservation I have about this method is that in a situation where the worker is just unable to talk to redis, it may complete the work twice.
The text was updated successfully, but these errors were encountered: