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

redis-cell support cluster? #30

Closed
cnsky2016 opened this issue Mar 19, 2019 · 6 comments
Closed

redis-cell support cluster? #30

cnsky2016 opened this issue Mar 19, 2019 · 6 comments

Comments

@cnsky2016
Copy link

hi,i want to know redis celll support redis cluster? according to https://redis.io/topics/modules-api-ref, i not found "getkeys-api" in your code.

@brandur
Copy link
Owner

brandur commented Mar 19, 2019

Hi @cnsky2016, unfortunately I don't have a good answer here — I don't think there any blockers to get it going on Redis Cluster, but I'm not sure about that.

according to https://redis.io/topics/modules-api-ref, i not found "getkeys-api" in your code.

Reading through the module docs, I don't think we need getkeys-api:

"getkeys-api": The command implements the interface to return the arguments that are keys. Used when start/stop/step is not enough because of the command syntax.

As of @xiezhenye's change yesterday in #29, we now correctly pass keystart/keystop/keystep, and because the command interface is relatively simple, I think those are enough and no more advanced keys interface is required.

(That said, I haven't tested.)

@profporridge
Copy link
Contributor

Hi, I have been trying to get this module working in a cluster. Unfortunately even after @xiezhenye's changes I wasn't able to to get the module working in a cluster. Once I added a call to 'replicateVerbatim' I was able to get the module to work as expected in a cluster - although this led to problems with the StackExchange client i'm using, since the client wasn't being made aware of the key it was unable to determine which node to select

@brandur
Copy link
Owner

brandur commented Mar 24, 2019

Thanks @profporridge.

although this led to problems with the StackExchange client i'm using, since the client wasn't being made aware of the key it was unable to determine which node to select

Is there something in the client that can be fixed there? I'm not sure I completely understand, but it seems like the interface might need to be tweaked so that it knows which arguments are keys when invoking custom commands.

@profporridge
Copy link
Contributor

The client needs to know what the key is so that it can determine which node to run the command on. It's entirely a client problem.

@xiezhenye
Copy link

xiezhenye commented Mar 29, 2019

The client needs to know what the key is so that it can determine which node to run the command on. It's entirely a client problem.

Both client and server should know which arguments are keys.

After server command info fixed, redis-cell can work correctly with redis-cli and Jedis.

@brandur
Copy link
Owner

brandur commented Mar 29, 2019

After server command info fixed, redis-cell can work correctly with redis-cli and Jedis.

Excellent!

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

4 participants