Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
A Proxy for redis servers, for failover and standby handling.

This branch is 33 commits behind master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


It's like haproxy except for redis.

Why RedisProxy?

Typically for every redis server we setup, we have a backup server setup as a slave of the main server.

If the Active Redis crashes or goes down for maintenance, we want the application to seamlessly use(read/write) data from the backup server. But the problem is once the backup takes over as active it will be out of sync with the original(master) and should become the slave of the current active. This is solved by redis-proxy, which proxies the active redis. It is also smart enough to issue slave of commands to machines that start up and make masters slave of no one.

This reduces the common redis slave master replication dance that needs to be done when bad stuff happens or maintenance of the servers are needed


  • Server Monitoring (to track masters and slaves)

  • Automatic slave upgrade on master failure

  • Supports Reads going to Slaves and Writes going to master. (Read/Write Forking)

  • Connection Pooling

  • Supports Pipelining

  • Honors Existing Master Slave Configurations( ie. if the masters and slaves are already setup then it will maintain the same configuration, instead of largescale movement of data)


We are in the process of testing it, it works for simple commands, but i have not tested and validated it against the whole set of redis commands. It is likely that commands like Pub sub don't work correctly(or at all).

Please consider this alpha software. All help and pull requests/ ideas are appreciated.


From NPM

Node.js and NPM are prerequistes. Here is the link to install both.

  • npm install -g redis-proxy

  • redis-proxy <path to config.json>

From Source

  • git clone

  • npm install

  • Modify the config/config.json

  • npm start


The standard scenario is each redis has a backup redis.

  • R1 backed by R2
  • R1 is slave of no one.
  • R2 is slave of R1

  • R1 Goes down ** We issue Slave of no one to R2 ** Make R2 the active redis

  • R1 Comes up.

    • We issue Slave of R2 to R1
    • R2 is still the active server
  • R2 Goes down

    • We make R1 Slave of no one
    • R1 is now the active redis.

If Both of them go down together, We just return errors and wait for one of them to come back on.

If no redis is available at startup we raise an exception and stop. (This will change for sure.)

There can be only one master in the system.

There can be multiple slaves. Each will become slave of the master, and on master doing down, one of the slave it randomly picked as master.

Redis-Proxy Stability

Redis proxy can become a single point of failure, If it goes down your redis servers will become inaccessible. There are 2 possible setups

  • Using Nodemon/Forever to keep the redis proxy up all the time

  • Have a backup redis-proxy on Elastic IP or Virtual IP and switch manually or using keepalived.

Limitations /TODOS

  • Benchmarks show about 3x drop in performance(Investigating it and will post a fix soon)

  • No support for Monitoring & pub/sub commands( There is no reason why this can't be supported)

  • Would be nice to have a small ui for showing errors and status of redis servers.

  • It currently only works as master/slave mode. And it's highly unlikely that there could be a switch to sharded mode.

  • Support for Read Write Splits

  • No downtime adding and removing slaves

Something went wrong with that request. Please try again.