-
Notifications
You must be signed in to change notification settings - Fork 348
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
request timeout[QUESTION] #558
Comments
Can you show me the minimum code that can reproduce the problem? If you use MGET command, these keys should locate on the same slot, even if the cluster scales up. In that case, the client connects and read/write a single node, no matter how large the cluster is. |
So sorry, but somehow, I missed this message. redis-plus-plus lazily creates connections, if it's the first time that these requests are sent to nodes, it needs to create connections to them. So if you have more nodes in clusters, you get higher latency. However, if all connections have been created, there should be no difference in latency, no matter how large the cluster is. Regards |
after cluster scale up,redis-plus-plus client request timeout increase;i use sw::redis::AsyncRedisCluster to get multi key,key nums no change,i want to kow why?
because get key need request more nodes? sw::redis::AsyncRedisCluster request redis server is not cocurrent?
The text was updated successfully, but these errors were encountered: