Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Replication and failover strategy for servers #47

Open
shumkov opened this issue Mar 2, 2012 · 4 comments
Open

Replication and failover strategy for servers #47

shumkov opened this issue Mar 2, 2012 · 4 comments
Labels
connection feature

Comments

@shumkov
Copy link
Owner

shumkov commented Mar 2, 2012

No description provided.

@till
Copy link
Collaborator

till commented May 12, 2012

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

@shumkov
Copy link
Owner Author

shumkov commented May 17, 2012

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

@marcguyer
Copy link

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

@marcguyer
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
connection feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@shumkov @till @marcguyer