I saw this plugin and would have used except it didn't work with the latest version of resque.

I've adapted your concept to work with the latest version. I think this is a bit cleaner and doesn't rely on alias_method_chain and uses the plugin hooks (except for the little bit of instance_eval at the end..)

I've put this in my config/initializers:
https://gist.github.com/667942

Cheers,
Adam

We added resque-mutli-job-forks to our project today, however, it appears that the workers disappear from the resque-web UI.

When the workers first start they show up in the UI, but after the fork for the second time, they all start to appear to die off. Looking at top the workers are obviously working and the jobs are being processed in the queue.

We are using resque 1.10.0

If you are interested in taking over the ownership of this project, please let me know.

I no longer use this project and am not interested in maintaining it.

Hey there!

I'm gearing up to work on Resque 2.0, and I'd like to coordinate better with plugin authors to make sure stuff doesn't break.

I'd like to know a few things:

1. Can I do something to help get you testing against edge Resque?
2. Are you monkey-patching anything in Resque currently? Can 2.0 expose an API to help you not have to do that any more?
3. Do you need any help in bringing your plugin up-to-date with the latest Resque?

Thanks!

Related: https://github.com/defunkt/resque/issues/880

Hi,

very nice plugin there. I've tried to track down a problem, where when plugin is enabled, the fork will happen in the child and the child will not exit. E.g. with time of 1 minutes per worker, I will see a fork happening initiallly, but then the next worker which is forked after 1 minute will have the child as parent process and the child will not exit.

Did you have any experiences with the side effecst, e.g. the stats are recorded per process and if breaking out the run loop it calls
unregister_worker (which will probably be a noop since the pid is not recorded any way).

Christian

Hey,

I'm in the need for exactly what your plugin provides!
Although I'm running Resque v1.10.0, not v1.7.1.
I can see in Resque v1.8.0 they depricated process and moved to using perform.

Any objection, if I make the changes for Resque >1.8.0?

Thanks
Luke

Can you clarify how resque workers should respond to signals when using resque-multi-job-forks?

I ask because it seems like my workers aren't responding to QUIT or if they are it is only after the fork time limit is reached.