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
Scan In cluster mode, other nodes cannot be scanned #4238
Comments
When I asked this question, I found the solution and the cause of the problem。 The reason is that the field client in the implementation of ScanCursor will affect the current entry node, resulting in the acquisition of connection is always the same node, and the node cannot be switched. In addition, I have mentioned mergeRequest, |
…e node redisson#4238 Signed-off-by: anyOne <caoleike@300.cn>
…e node redisson#4238 Signed-off-by: Old Cao <clk5858@163.com> Signed-off-by: anyOne <caoleike@300.cn>
…ly a single node redisson#4238 Signed-off-by: old Cao <clk5858@163.com>
…canned,Not only a single node redisson#4238 Signed-off-by: old Cao <clk5858@163.com>
Fixed! Thanks for report |
Expected behavior
The iterator returned by SCAN can scan all nodes
Actual behavior
But only one node will be scanned
Steps to reproduce or test case
In cluster mode, run the scan command
Redisson version
All versions have this problem
Redisson configuration
Cluster mode: Three master and three slave
The text was updated successfully, but these errors were encountered: