If you're using rails, and have a full library of gems and plugins, it can be quite expensive to launch individual workers. What seems to work well is launching a single supervisor process, and forking your workers from that. I currently do this from a cronjob, but what would be nicer would be to make the supervisor a worker that forks other workers in response to messages. That approach could be combined with what Ask wrote below, to enable the supervisor to keep an eye on the workers it spawns.
On Sun, Nov 22, 2009 at 11:26 AM, Ask Bjørn Hansen <[email protected]>wrote: > > > On Nov 20, 4:05 pm, gonzoprosperity <[email protected]> wrote: > > > I am wondering how people have their background workers monitored and > > controlled. We usually use God to monitor jobs but I cannot seem to > > get it to play nice with the workers. > > Graham made a plugin for nagios that we use: > > > http://search.cpan.org/dist/Nagios-Plugin-Beanstalk/lib/Nagios/Plugin/Beanstalk.pm > > Rather than monitor the workers directly, we check with beanstalkd > that there's a worker for each queue and (when appropriate) that the > oldest job isn't older than whatever threshold is appropriate. > > > - ask > > -- > > You received this message because you are subscribed to the Google Groups > "beanstalk-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<beanstalk-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/beanstalk-talk?hl=. > > > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=.
