We\'re running Ruby workers across a large number of machines using Resque. Every once in a while, we see segmentation faults in our Resque worker processes. It\'s hard to debug these, because they\'r
I\'m adding Resque-Scheduler in my app on Heroku So... I need ONE alone and distinct worker acting as the scheduler and
I have an app that sets creates EC2 instances - I have a resque ta开发者_JAVA百科sk that will configure the server (via ssh) once it\'s up and running:
Here is the stack trace which appears on resque-web interface: http://gist.github.com/396893 There you can check some gem versions that I was using.
I\'m currently moving my application from a Linode setup to EC2.Redis is currently installed on a remote instance with various worker instances interacting with the queue.Thats all going fantastic.
I\'m having a runtime errror when i\'m looking at the \"workers\" tab on resque-web (localhost). Everything else works.
Does anyone have or know of a guide for how to migrate from Delayed Job to Resque? I can\'t fi开发者_运维知识库nd any on Google and figure I must not be the first one doing this. Just a general list o
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expertise, but this question will likely solicit debate, a
I have resque-scheduler working fine in a rails app. Now I need to be able to track status and remove jobs from the queue. I had a brief look at resque-sta开发者_如何转开发tus and, from what I saw, if
The GitHub guys recently released their background processing app which uses Redis: http://github.com/defunkt/resque
加载中,请稍侯......