As you can see from the attached image, I\'ve got a couple of workers that seem to be stuck. Those processes shouldn\'t take longer than a couple of secon开发者_JAVA技巧ds.
I\'ve got Redis/Resque installed but I\'m having a hard time starting/restarting it from Capistrano when I deploy.
I\'ve having a bizarre issue with a resque job that I\'m wondering if anyone else has run into. We\'re running resque under jruby 1.6.2
While I restart resque workers during deploy if new job comes in, then these jobs are set as queued in resque-status but it\'s not actually queued in resque. So my jobs are lost.
I run a server monitoring site for a video game. It monitors thousands of servers (currently 15,000 or so).
I need to start 4 resque workers so i used following command bundle exec rake environment resque:workers RAILS_ENV=production COUNT=4 QUEUE=* VERBOSE=1 PIDFILE=tmp/pids/resque_worker.pid>> log
On my dev machine, I am able to type resque-web in a console and it launches a new tab on my browser which shows the Resque interface.
Because of heavy background process, we need multiple servers that just do background processes. We are using resque for handling background jobs. Since the res开发者_开发百科que workers on each
Using resque, I would like to specify a namespace and be able to see the workers in resque-web The resque rake task is started this way:
I am processing my background jobs using Resque. My model looks like开发者_如何转开发 this class SomeClass
加载中,请稍侯......