resque

I have site running rails application and resque workers running in production mode, on Ubuntu 9.10, Rails 2.3.4, ruby-ee 2010.01, PostgreSQL 8.4.2 Workers constantly raised errors: PGError: server closed the connection unexpectedly. My best guess is that master resque process establishes connection to db (e.g. authlogic does that when use User.acts_as_authentic), while loading rails app classes, and that connection becomes corrupted in fork()ed process (on exit?), so next forked children get kind of broken global ActiveRecord::Base.connection I could reproduce very similar behaviour with this

I'm building an application that allows for large amounts of photo uploads at once, and wanted to know what the best setup would be to tackle this. This is what I am using so far: Jquery File Upload: allows users to drag and drop images CarrierWave: Processes images and resizes them with ImageMagick Amazon S3: CarrierWave uploads images to Amazon S3 through Fog Heroku: for hosting I'd like to allow users to be able to drag and drop a large amount of images onto a page, and then navigate to other pages while the upload is going on in the background. I'd also like pictures to appear as they

The GitHub guys recently released their background processing app which uses Redis: http://github.com/defunkt/resque http://github.com/blog/542-introducing-resque I have it working locally, but I'm struggling to get it working in production. Has anyone got a: Capistrano recipe to deploy workers (control number of workers, restarting them, etc) Deployed workers to separate machine(s) from where the main app is running, what settings were needed here? gotten redis to survive a reboot on the server (I tried putting it in cron but no luck) how did you work resque-web (their excellent monitoring

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 seconds. I'm not sure why they won't clear or how to manually remove them. I'm on Heroku using Resque with Redis-to-Go and HireFire to automatically scale workers. None of these solutions worked for me, I would still see this in redis-web: 0 out of 10 Workers Working Finally, this worked for me to clear all the workers: Resque.workers.each {|w| w.unregister_worker} In your console: queue_name = "process_numbers" Resque.redis.del "queue:#{queue_name}

How can I create and use background jobs in node.js? I've come across two libs (node-resque and node-worker) but would like to know if there's something more used. Alfred I did some research on this and I would do it like this. Setup beanstalkd Install beanstalkd . Another message queue, BUT this one supports DELAYED PUTS . If you compile from source it is going to be a little harder because it depends on libevent (like memcached). But then again, I don't think you have to compile it from source, because there are a lot of binary packages available. For example on Ubuntu you can install

I am currently using Resque for my background process but recently I heard a lot of huff-buff about sidekiq . Could anybody compare/differentiate? In particular I would like to know is there a way to monitor programmatically whether a job is completed in sidekiq Resque: Pros: does not require thread safety (works with pretty much any gem out there); has no interpreter preference (you can use any ruby); Resque currently supports MRI 2.3.0 or later loads of plugins. Cons runs a process per worker (uses more memory); does not retry jobs (out of the box, anyway). Sidekiq: Pros runs thread per