Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support redis failover in standalone #694
If we are ok with above points then I can go ahead and implement failover with redis standalone connection.
@nynymike giving cache redundancy by having some sort of replication topology requires a smarter jedis client to handle one of the servers throwing an error and refusing connections. As it stands, twemproxy can't route traffic to a redis-cluster topology and using something like dynomitedb for replicating data instead doesn't give twemproxy the necessary signals it needs to know a redis-server is down.
We wouldn't need to use twemproxy if oxAuth could handle recognizing a server isn't responding and moving on to another in it's
There's currently not really any other option for giving a highly available cache system that I can find. The expectation seems to be that some client side error handling should be embedded.