Resque::Plugins::RealSerialQueues

This plugin modifies resque's' job reservation process to first check if there is another job from the same queue as the potential job currently being processed by one of your workers and tells the worker to check again after its sleep cycle.

It is primarily meant to be used to queue long running background jobs across multiple queues in conjunction with something like resque-scheduler

A key difference between this and resque-lonely_job is that the queue is not touched when we check to see if we can process the job (thus there is no danger of your queues getting processed in a different order). However, because we must check all the workers currently working on the system this plugin may not scale well to large numbers of workers.

This gem is under active development - so please use caution if your jobs are responsible for controlling rocket ships or providing food and shelter to young children.

Installation

Add this line to your application's Gemfile:

gem 'resque-real-serial-queues'

And then execute:

$ bundle

Or install it yourself as:

$ gem install resque-real-serial-queues

Usage

Just load up plugin somewhere in your project's initializers:

require 'resque_real_serial_queues'

In rails adding

resque_real_serial_queues.rb

to your

config/initializers

directory with the above line should do the trick.

Note that this will currently affect all queues

Configuration and Adding Non-Serial Queues

By default all queues are considered serial if you just install the plugin. If you'd like to have some queues that do not get processed serially - you can add them via a configuration option after you require the plugin:

# you can pass it straight in as a hash
Resque::Plugins::RealSerialQueues.config = {
  non_serial_queues: ['non_serial_queue_one', 'non_serial_queue_two']
}

# or you can place it in a config file
require 'yaml'

Resque::Plugins::RealSerialQueues.config = YAML.load_file('your_config_file.yml')

If you choose to use a YAML config file - the queue names must be specified as a list:

non_serial_queues:
  - non_serial_queue_one
  - non_serial_queue_two

Not specifying any configuration will cause all queues to be processed serially.

Contributing

1. Fork it ( https://github.com/[my-github-username]/resque-real-serial-queues/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request