You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: