Sidekiq::Rerouting

A Sidekiq extension to set Sidekiq jobs to be rerouted to a different queue based on the job ID or job class.

Install the gem and add to the application's Gemfile by executing:

bundle add sidekiq-rerouting

If bundler is not being used to manage dependencies, install the gem by executing:

gem install sidekiq-rerouting

From a console (Rails console, or the like) you need a Sidekiq::Rerouting::Client instance, which is used to #reroute a job, or job class to be disposed.

client = Sidekiq::Rerouting::Client.new

A job marked to be rerouted means it will be re-enqueued to the destination queue when it's picked up.

# Mark a specific Job to be rerouted by specifying its job ID
client.reroute("different_queue", :jid, some_job_id)

# Mark an entire job class to be rerouted
client.reroute("different_queue", :class, "SomeJobClass")

A job or job class can also be removed from rerouting via a corresponding API. This only takes effects for jobs enqueued after the API call. Reroute the jobs back to its original queue to affect the previously rerouted jobs still in the queue.

# Unmark a specific Job for rerouting by specifying its job ID
client.remove_rerouting(:jid, some_job_id)

# Unmark an entire job class for rerouting
client.remove_rerouting(:class, "SomeJobClass")

# Force previously rerouted job class/jid to its original queue
client.reroute("original_queue", :jid, some_job_id)
client.reroute("original_queue", :class, "SomeJobClass")

Clearing all reroutes marks can be done in one fell swoop as well.

client.remove_rerouting_for_all

With sidekiq-rerouting installed, register its Sidekiq server middleware. Typically this is done via config/initializers/sidekiq.rb in a Rails app.

Sidekiq.configure_server do |config|
  config.server_middleware do |chain|
    chain.add Sidekiq::Rerouting::ServerMiddleware
  end
end

This piece of middleware checks each job, after it's been dequeued, but before its #perform has been called, to see if it should be rerouted. If the job is marked for rerouting (by job ID or job class), a new job (with the same job ID) is enqueued into the intended destination and the current job exits early.

If you'd like to do something when a job is rerouted, you can optionally pass in an object that responds to .call (like a Proc) when adding the middleware:

Sidekiq.configure_server do |config|
  config.server_middleware do |chain|
    chain.add(Sidekiq::Rerouting::ServerMiddleware, on_reroute: -> { |job:, old_queue:, new_queue:|
      puts "Job with jid=#{job["jid"]} was rerouted from #{old_queue} to #{new_queue}"
    })
  end
end

It yields the following keyword arguments:

• job: the serialized job that is being rerouted; see Sidekiq's docs for more details.
• old_queue: the queue from which the job is being rerouted.
• new_queue: the queue to which the job is being rerouted.

If you're using Sidekiq Pro's Batch feature you need to be sure to insert the rerouting middleware after the Batch middleware. This will ensure the batch can be re-opened, and the rereouted job added to it.

Sidekiq.configure_server do |config|
  config.server_middleware do |chain|
    chain.insert_after(Sidekiq::Batch::Server, Sidekiq::Rerouting::ServerMiddleware)
  end
end

By default all Jobs are reroutable. However, checking if a specific job should be rerouted is not free; it requires round trip(s) to Redis. Therefore, you might want to make some jobs non-reroutable to avoid these extra round trips. Or because there are some Jobs that simply should never be rerouted for… reasons.

This is done via a job's sidekiq_options.

sidekiq_options reroutable: false

With that in place, the server middleware will ignore the Job, and pass it down the middleware Chain. No extra Redis calls, no funny business.

After checking out the repo, run bin/setup to install dependencies. Then, run bin/rspec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bin/rake install. To release a new version, update the version number in version.rb, and then run bin/rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Bug reports and pull requests are welcome on GitHub at https://github.com/hibachrach/sidekiq-rerouting. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

The gem is available as open source under the terms of the MIT License.

Everyone interacting in the Sidekiq::Rerouting project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

• sidekiq-disposal