Lock-down gemspec to redis 2.2.x in light of upcoming redis 3.x release. Once sufficient testing
has been done with the 3.x release, I will relax the constraint in the gemspec.
Add environment-scoped configuration file support (oleriesenberg)
Added a way to gracefully shutdown/reconnect a RedisFailover::Client. (#13)
Upgraded to latest ZK version that supports forking.
Handle case where the same RedisFailover::Client is referenced by a #multi block (#14)
Fix method signature for RedisFailover::Client#respond_to_missing? (#12)
Added YARD documentation.
Improve ZooKeeper client connection management.
Upgrade to latest ZK gem stable release.
Added manual failover support (can be initiated via RedisFailover::Client#manual_failover)
When new master promotion occurs, make existing slaves point to new candidate before promoting new master.
Add support for specifying command-line options in a config.yml file for Node Manager.
Upgrade to 0.9 version of ZK client and cleanup ZK connection error handling.
Add support for running multiple Node Manager processes for added redundancy (#4)
Add support for specifying a redis database in RedisFailover::Client (#5)
Improved Node Manager command-line option parsing
No longer use problematic ZK#reopen.
Handle more ZK exceptions as candidates for reconnecting the client on error.
Add safety check to actively purge redis clients if a RedisFailover::Client hasn't heard from the Node Manager in a certain time window.
Always try to create path before setting current state in Node Manager.
More explicit rescuing of exceptions.
More logging around exceptions
Handle re-watching on client session expirations / disconnections
Use an ephemeral node for the list of redis servers
redis_failover is now built on top of ZooKeeper! This means redis_failover enjoys all of the reliability, redundancy, and data consistency offered by ZooKeeper. The old fragile HTTP-based approach has been removed and will no longer be supported in favor of ZooKeeper. This does mean that in order to use redis_failover, you must have ZooKeeper installed and running. Please see the README for steps on how to do this if you don't already have ZooKeeper running in your production environment.
No longer force newly available slaves to master if already slaves of that master
Honor a node's slave-serve-stale-data configuration option; do not mark a sync-with-master-in-progress slave as available if its slave-serve-stale-data is disabled
Change reachable/unreachable wording to available/unavailable
Added node reconciliation, i.e. if a node comes back up, make sure that the node manager and the node agree on current role
More efficient use of redis client connections
Raise proper error for unsupported operations (i.e., those that don't make sense for a failover client)
Properly handle any hanging node operations in the failover server
Added background monitor to client for proactively detecting changes to current set of redis nodes
Added retry support for contacting failover server from client
Client now verifies proper master/slave role before attempting operation