We need workaround since latest resque does not support PIDFILE env

Created by: dzaporozhets

Created by: dzaporozhets

This commit adds rake task to stop workers 5cd82384

By Administrator on 2012-12-26T09:24:15 (imported from GitLab)

Created by: riyad

Many people have switched to Sidekiq.

By Administrator on 2012-12-26T11:02:57 (imported from GitLab)

Created by: dzaporozhets

@Riyad looks nice. But its now an answer for us. At least until v5.0

By Administrator on 2012-12-26T11:08:57 (imported from GitLab)

Created by: riyad

Why not? You still need Redis to be installed, but you swap Resque with Sidekiq as Gem dependency. We need to rewrite some code, but it's all "internal". Am I mistaken?

By Administrator on 2012-12-26T11:20:50 (imported from GitLab)

Created by: dzaporozhets

gem and rewrite ok is not a problem for us :) Dont forget we have users with init.d scripts which use resque. And docs.

By Administrator on 2012-12-26T11:26:52 (imported from GitLab)

Created by: riyad

Well actually the "interface" is a pid file and a rake task ... so nothing Resque specific. ;)

By Administrator on 2012-12-26T11:43:55 (imported from GitLab)

Created by: vsizov

also we have resque monitor in admin area.

By Administrator on 2012-12-26T12:05:32 (imported from GitLab)

Created by: dzaporozhets

@Riyad I will try sidekiq

By Administrator on 2012-12-27T08:29:49 (imported from GitLab)

Created by: riyad

persuasion: success! ;)

By Administrator on 2012-12-27T16:02:48 (imported from GitLab)

Created by: koenpunt

@randx Where have you found that PIDFILE is not supported anymore? Resque's documentation states:

Running in the background

(Only supported with ruby >= 1.9). There are scenarios where it's helpful for the resque worker to run itself in the background (usually in combination with PIDFILE). Use the BACKGROUND option so that rake will return as soon as the worker is started.

$ PIDFILE=./resque.pid BACKGROUND=yes QUEUE=file_serve \
    rake environment resque:work

So I guess adding BACKGROUND is a solution?

I'll try some things and submit a PR afterwards.

By Administrator on 2013-01-03T15:03:08 (imported from GitLab)

Created by: koenpunt

I see that PIDFILE isn't even used in the code of the resque gem, so that explains something.. And explicitly writing the process id doesn't work either, because apparently the master process dies after it has spawn the workers..

By Administrator on 2013-01-03T15:33:10 (imported from GitLab)

Created by: dzaporozhets

switched to sidekiq

By Administrator on 2013-01-09T17:31:05 (imported from GitLab)

Created by: dzaporozhets

@Riyad also first impression of sidekiq - its awesome :)

By Administrator on 2013-01-09T22:35:44 (imported from GitLab)

Created by: riyad

No wonder, "everybody" is using it. :P

By Administrator on 2013-01-09T22:41:31 (imported from GitLab)