-
Notifications
You must be signed in to change notification settings - Fork 447
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
Cluster #43
Comments
@misiek08 I don't have the time to look into this and I'll rely on contributions :) |
So we need to wait, right? :) |
Yes. I have put this into my TODO list. This is indeed a good thing to have. |
come on misiek08 💯 |
come on |
Maybe i'm wrong, but doesn't redis have builtin clustering functionality since version 3.0? Can't we rely on that? |
@bjoe2k4 yes it have, but client need to implement few responses from Redis to fully support cluster. Redis have built in only semi-routing which tells client where to ask for data if client connected to wrong node at first. |
Guys, there are two pull requests implementing cluster-related features on the client side. Have you checked them out? See |
I see only one is totally cluster-related but I don't understand a part of code there.... Looks like there are 2 hard-coded limits for cluster count (20) and nodes count in cluster (500). Or Lua is better than I think and my comment it's useless :) I had half-year break in Lua and nginx-related development... |
I will add this to here as a reminder that implementing a cluster support is not something that can be done ligthly, many questions needs to be answered, a lot of design decisions need to be made: |
+1 |
+1 |
Actually there are some unofficial clients offer part of the redis-cluster support. For example, like this one: |
Hi! Is it possible to implement cluster functionality to core of this library? I'm not sure if I am able to do it myself, I tried, but code looks bad and it fails sometimes.
The text was updated successfully, but these errors were encountered: