1
0
Fork 0
mirror of https://github.com/deanpcmad/sidekiq-limit_fetch.git synced 2022-11-09 13:54:36 -05:00
Sidekiq strategy to support an advanced queue control – limiting, pausing, blocking, querying
Find a file
2013-05-22 11:42:56 +04:00
lib/sidekiq Separate probed and busy indicators for queue 2013-05-22 11:42:56 +04:00
spec Separate probed and busy indicators for queue 2013-05-22 11:42:56 +04:00
.gitignore Initial implementation 2013-01-11 14:56:41 +04:00
.travis.yml Travis has fixed jruby issues 2013-03-13 12:36:34 +04:00
Gemfile Change rubygems to secure version 2013-03-10 13:39:27 +04:00
LICENSE.txt Initial implementation 2013-01-11 14:56:41 +04:00
Rakefile Run travis tests 2013-01-24 18:15:55 +04:00
README.md Use global mode by default 2013-04-25 14:21:05 +04:00
sidekiq-limit_fetch.gemspec Release new version of sidekiq with latest sidekiq support 2013-05-22 10:32:20 +04:00

Description

Sidekiq strategy to support a granular queue control limiting, pausing, blocking, querying.

Build Status Gem Version Dependency Status Code Climate

Installation

Add this line to your application's Gemfile:

gem 'sidekiq-limit_fetch'

Usage

Limits

Specify limits which you want to place on queues inside sidekiq.yml:

  :limits:
    queue_name1: 5
    queue_name2: 10

Or set it dynamically in your code:

  Sidekiq::Queue['queue_name1'].limit = 5
  Sidekiq::Queue['queue_name2'].limit = 10

In these examples, tasks for the queue_name1 will be run by at most 5 workers at the same time and the queue_name2 will have no more than 10 workers simultaneously.

Ability to set limits dynamically allows you to resize worker distribution among queues any time you want.

Busy workers by queue

You can see how many workers currently handling a queue:

  Sidekiq::Queue['name'].busy # number of busy workers

Pauses

You can also pause your queues temporarely. Upon continuing their limits will be preserved.

  Sidekiq::Queue['name'].pause # prevents workers from running tasks from this queue
  Sidekiq::Queue['name'].paused? # => true
  Sidekiq::Queue['name'].unpause # allows workers to use the queue

Blocking queue mode

If you use strict queue ordering (it will be used if you don't specify queue weights) then you can set blocking status for queues. It means if a blocking queue task is executing then no new task from lesser priority queues will be ran. Eg,

  :queues:
    - a
    - b
    - c
  :blocking:
    - b

In this case when a task for b queue is ran no new task from c queue will be started.

You can also enable and disable blocking mode for queues on the fly:

  Sidekiq::Queue['name'].block
  Sidekiq::Queue['name'].blocking? # => true
  Sidekiq::Queue['name'].unblock

Advanced blocking queues

You can also block on array of queues. It means when any of them is running only queues higher and queues from their blocking group can run. It will be easier to understand with an example:

  :queues:
    - a
    - b
    - c
    - d
  :blocking:
    - [b, c]

In this case tasks from d will be blocked when a task from queue b or c is executed.

You can dynamically set exceptions for queue blocking:

  Sidekiq::Queue['queue1'].block_except 'queue2'

Thanks

Sponsored by [Evil Martians]. [Evil Martians]: http://evilmartians.com/