-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
CROSSSLOT keys issue when using redis cluster #709
Comments
Hi, thanks for issue! Yes, please do open a PR 🙏 I'm thinking if there's a way we could avoid referencing Redis::Namespace directly. Or if we could rewrite this method without using rename. That way, we wouldn't need to worry about Hash tags. I'll do some further investigation. it's been a while since I did the original PR. |
We considered the below approach of using
|
I'll look into this some time this week. I had some personal issues that kept me away 😓 |
Closed by #710 |
The change introduced as part of this PR does not work with the Redis Cluster setup. The
redis.rename
method call raises an error with the messageCROSSSLOT Keys in request don't hash to the same slot
.Solution:
Can we port the above changes into the gem?
The text was updated successfully, but these errors were encountered: