Replication and failover strategy for servers

shumkov / rediska

No longer maintained. Full-featured PHP client for key-value database Redis

http://rediska.geometria-lab.net

BSD 3-Clause "New" or "Revised" License

267 stars 68 forks source link

Replication and failover strategy for servers #47

Open shumkov opened 12 years ago

till commented 12 years ago

I wonder if this shouldn't be handled in code but by a TCP loadbalancer like haproxy?

shumkov commented 12 years ago

No, its 'readOnly', 'writeOnly' options for servers

marcguyer commented 8 years ago

What happens currently if 2+ servers are configured with consistent distribution hashing (ketama) but one of the servers becomes unavailable?

marcguyer commented 8 years ago

According to my research and tests, there is zero special handling for server failure. The consistent key hashing will distribute cache data across a pool of servers. However, if a member of the pool is unavailable, and the key you're operating on hashes to that server, you have a fatal situation for that particular key.