-
Notifications
You must be signed in to change notification settings - Fork 30
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
Problem connecting with Redis Cluster #39
Comments
oh interesting. I did not know also that was a thing .Thanks for linking the original issue. So what fixes it? I am unclear what moves does? seems that we would need to restart the pool to fix it? |
left some question in the MR. Happy to look at it more next week. |
@epinault I think it is easier if eredis_cluster can be used for redis_cluster case and for normal redis, the eredis package Basically, to change the Redix dependency to eredis + eredis_cluster in favor of more features |
yea but that package is not getting a lot maintenance. I dont see any releases in 2 years but did notice a merge like 7 months ago. So I am worried about how maintained that library is. But we could create a configurable backend maybe so you can pick between the best of both world when needed? Redix, Eredis or Eredis cluster as possible backend? Though I am not sure how the eredis cluster works to be honest and would need to see how it fits . Otherwise we could create a special backend in a different package |
i have release 7.x that has much better performances at this time compare to the old release. |
Describe the bug
Recently we're trying to connect a redis cluster for use with Hammer, but we got an error that comes from Redix:
Following this: whatyouhide/redix#240, looks like this error comes from
Redix
that doesn't have support for the redis clustermoved errors
.Not sure what is the best way to handle this, I think we can handle the errors coming from
Redix
and create a new connection for the correct node and usingredix
we can send and get the data.The text was updated successfully, but these errors were encountered: