-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Cluster client logs info for command not found #1069
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
Comments
github.com/go-redis/redis/tree/v6.15.2 |
I guess that is possible if you say so. But why does it happen? |
Hey, I'm seeing this as well. Any idea what the reason is? |
@vmihailenco This has started happening since #1056. Before #1056, Now |
Okay, but we do we need a cluster state to retrieve commands info? ClusterClient is created with at least 1 healthy node which should be enough to retrieve commands info... |
@vmihailenco Cluster state isn't necessary. Refreshing cluster state lazily creates the nodes (
|
Is it possible to compute the slot of the command without depending on COMMAND? |
Good call - I've sent a fix. |
Uh oh!
There was an error while loading. Please reload this page.
Version: 4a3dbb3
Using the cluster client, the internal logger is logging a lot of lines on commands. I believe cmdsInfo is being ran before cluster state has synced, which results in cmdsInfoCache storing an empty result.
When this happens, a random node is always chosen on the first attempt, which has a high chance of getting a
MOVED
responseOutput
Example
The text was updated successfully, but these errors were encountered: