Empty queue or stacked active jobs after reboot

[gavrochelegnou]

Hi,

I noticed two issues with "improper" shutdown of kue, typically after a "reboot" command.
After the first reboot my queue was still there, a job from the queue succesfully passed as "active" but the job running before the reboot was still in "active" state but was not running at all.
I think it should have restarted or been marked as "Failed" ?
(I noticed the same behavior when running kue from command line and hiting CTRL+C)

I tried a second reboot just after that and then everything was empty (queue/active/failed/...)
I noticed some errors related to redis (lost connection i suppose) but they were not logged so can't paste them here, may try again if needed.

Is there a specific way to reboot the server and have kue handle it correctly ?

Thanks a lot for the good work !

[sebicas]

I am having the same problems.

[spolu]

same here

[gkrcode]

Same here
@gavrochelegnou , @sebicas , @spolu find any solution ?

[gavrochelegnou]

Nop, we moved to gearman http://gearman.org/ , a little trickier to setup and missing a nice ajax interface, but much more stable for managing queues and jobs ...
For our problem i think it might be link to redis persistence configuration, but we didn't investigate further ...
Good luck !

[spolu]

Here we ditched kue for a much simpler solution we coded and based on mongoDB

[sebicas]

Nop :( I use flushdb directly in redis to have a fresh start every couple weeks...
But you only can do that if have no inactive task pending of course.

[gkrcode]

Thanks all :)

[sveisvei]

Used alot of time debugging my app because of this issue, anoying. Because of this, somehow the data was 1 index off. Guess we need a pullreq :)

[bulkan]

This issue is a duplicate of #121 and related to #105

@drudge @visionmedia please close this issue 😄