Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A distributed semaphore and mutex built on Redis.
branch: master

Merge pull request #31 from RosieApp/fix-available-count

Fixing available resources for non-locked semaphores
latest commit 61d6f375b6
David Verhasselt authored

Code Climate Build Status


Implements a mutex and semaphore using Redis and the neat BLPOP command.

The mutex and semaphore is blocking, not polling, and has a fair queue serving processes on a first-come, first-serve basis. It can also have an optional timeout after which a lock is unlocked automatically, to protect against dead clients.

For more info see Wikipedia.


Create a mutex:

s =, :host => "localhost")
s.lock do
  # We're now in a mutex protected area
  # No matter how many processes are running this program,
  # there will be only one running this code block at a time.

While our application is inside the code block given to s.lock, other calls to use the mutex with the same name will block until our code block is finished. Once our mutex unlocks, the next process will unblock and be able to execute the code block. The blocking processes get unblocked in order of arrival, creating a fair queue.

You can also allow a set number of processes inside the semaphore-protected block, in case you have a well-defined number of resources available:

s =, :resources => 5, :host => "localhost")
s.lock do
  # Up to five processes at a time will be able to get inside this code
  # block simultaneously.

You're not obligated to use code blocks, linear calls work just fine:

s =, :host => "localhost")
s.unlock  # Don't forget this, or the mutex will stay locked!

If you don't want to wait forever until the semaphore releases, you can pass in a timeout of seconds you want to wait:

if s.lock(5) # This will only block for at most 5 seconds if the semaphore stays locked.
  puts "Aborted."

You can check if the mutex or semaphore already exists, or how many resources are left in the semaphore:

puts "This semaphore does exist." if s.exists?
puts "There are #{s.available_count} resources available right now."

When calling unlock, the new number of available resources is returned:

sem.unlock # returns 1
sem.available_count # also returns 1

In the constructor you can pass in any arguments that you would pass to a regular Redis constructor. You can even pass in your custom Redis client:

r = => "localhost", :db => 222)
s =, :redis => r)

If an exception happens during a lock, the lock will automatically be released:

  s.lock do
    raise Exception
  s.locked? # false


To allow for clients to die, and the token returned to the list, a stale-check was added. As soon as a lock is started, the time of the lock is set. If another process detects that the timeout has passed since the lock was set, it can force unlock the lock itself.

There are two ways to take advantage of this. You can either define a :stale_client_timeout upon initialization. This will check for stale locks everytime your program wants to lock the semaphore:

s =, :redis = r, :stale_client_timeout => 5) # in seconds

Or you could start a different thread or program that frequently checks for stale locks. This has the advantage of unblocking blocking calls to Semaphore#lock as well:

normal_sem =, :host => "localhost") do
  watchdog =, :host => "localhost", :stale_client_timeout => 5)

  while(true) do
    sleep 1

sleep 5
normal_sem.locked? # returns false

normal_sem.lock(5) # will block until the watchdog releases the previous lock after 1 second


Wait and Signal

The methods wait and signal, the traditional method names of a Semaphore, are also implemented. wait is aliased to lock, while signal puts the specified token back on the semaphore, or generates a unique new token and puts that back if none is passed:

# Retrieve 2 resources
token1 = sem.wait
token2 = sem.wait


# Put 3 resources back

sem.available_count # returns 3

This can be used to create a semaphore where the process that consumes resources, and the process that generates resources, are not the same. An example is a dynamic queue system with a consumer process and a producer process:

# Consumer process
job = semaphore.wait

# Producer process
semaphore.signal(new_job) # Job can be any string, it will be passed unmodified to the consumer process

Used in this fashion, a timeout does not make sense. Using the :stale_client_timeout here is not recommended.

Use local time

When calculating the timeouts, redis-semaphore uses the Redis TIME command by default, which fetches the time on the Redis server. This is good if you're running distributed semaphores to keep all clients on the same clock, but does incur an extra round-trip for every action that requires the time.

You can add the option :use_local_time => true during initialization to use the local time of the client instead of the Redis server time, which saves one extra roundtrip. This is good if e.g. you're only running one client.

s =, :redis = r, :stale_client_timeout => 5, :use_local_time => true)

Redis servers earlier than version 2.6 don't support the TIME command. In that case we fall back to using the local time automatically.


redis-semaphore supports an expiration option, which will call the EXPIRE Redis command on all related keys (except for grabbed_keys), to make sure that after a while all evidence of the semaphore will disappear and your Redis server will not be cluttered with unused keys. Pass in the expiration timeout in seconds:

s =, :redis = r, :expiration => 100)

This option should only be used if you know what you're doing. If you chose a wrong expiration timeout then the semaphore might disappear in the middle of a critical section. For most situations just using the delete! command should suffice to remove all semaphore keys from the server after you're done using the semaphore.


$ gem install redis-semaphore


$ bundle install
$ rake


0.2.4 January 11, 2015

  • Fix bug with TIME and redis-namespace (thanks sos4nt!).
  • Add expiration option (thanks jcalvert!).
  • Update API version logic.

0.2.3 September 7, 2014

  • Block-based locking return the value of the block (thanks frobcode!).

0.2.2 June 16, 2014

  • Fixed bug in all_tokens (thanks presskey!).
  • Fixed bug in error message (thanks Dmitriy!).

0.2.1 August 6, 2013

  • Remove dependency on Redis 2.6+ using fallback for TIME command (thanks dubdromic!).
  • Add :use_local_time option

0.2.0 June 2, 2013

  • Use Redis TIME command for lock timeouts (thanks dubdromic!).
  • Version increase because of new dependency on Redis 2.6+

0.1.7 April 18, 2013

  • Fix bug where release_stale_locks! was not public (thanks scomma!).

0.1.6 March 31, 2013

  • Add non-ownership of tokens
  • Add stale client timeout (thanks timgaleckas!).

0.1.5 October 1, 2012

  • Add detection of Redis::Namespace definition to avoid potential bug (thanks ruud!).

0.1.4 October 1, 2012

  • Fixed empty namespaces (thanks ruurd!).

0.1.3 July 9, 2012

  • Tokens are now identifiable (thanks timgaleckas!).

0.1.2 June 1, 2012

  • Add redis-namespace support (thanks neovintage!).

0.1.1 September 17, 2011

  • When an exception is raised during locked period, ensure it unlocks.

0.1.0 August 4, 2011

  • Initial release.


David Verhasselt -


Thanks to these awesome people for their contributions:

Something went wrong with that request. Please try again.