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.

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

Corvus key distribution algorithm #143

Open
inigoml opened this issue May 8, 2018 · 2 comments
Open

Corvus key distribution algorithm #143

inigoml opened this issue May 8, 2018 · 2 comments

Comments

@inigoml
Copy link

inigoml commented May 8, 2018

Hi.
We are currently working with nutcracker (twemproxy) in order to create our own redis cluster. However we are experiencing some scaling problems due to twemproxy is not multithreaded. In order to start testing with Corvus using the same existing cluster, we would like to know which key distribution algorithm is being used currently in order to know if we can use the same existing cluster to test in parallel both solutions.
If corvus use ketama as algorithm we would use is without any complex migration procedure for our persistent keys.

Thanks in advance.

@maralla
Copy link
Contributor

maralla commented May 8, 2018

Corvus is a proxy for cluster mode Redis(>=3.0). So the key distribution algorithm is determined by the sharding mechanism of Redis. And I think you have to prepare a migration process as the ketama algorithm is not used by Redis.

@inigoml
Copy link
Author

inigoml commented May 9, 2018

OK, totally understood. Twemproxy does not use redis cluster and so distribution is done by proxy.
If we want to migrate to Corvus we should take care of non-persistent keys currently inside our twmproxied redis cluster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants