redis_version:5.0.8 redis_git_sha1:00000000 redis_git_dirty:0 redis_build_id:23e68a8e0defcb65 redis_mode:cluster os:Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64 arch_bits:64 multiplexing_api:epoll atomicvar_api:atomic-builtin gcc_version:4.8.5
when we do redis-cluster add nodes and reshard , the command exit quickly without any prompt. `
redis-cli --cluster rebalance 192.168.6.90 6382 --cluster-use-empty-masters Could not connect to Redis at 192.168.6.92:6379: Connection refused
Performing Cluster Check (using node 192.168.6.90:6382) [OK] All nodes agree about slots configuration. Check for open slots... Check slots coverage... [OK] All 16384 slots covered. Rebalancing across 39 nodes. Total weight = 39.00 Moving 34 slots from 192.168.6.93:6380 to 192.168.6.89:6379
Moving 34 slots from 192.168.6.93:6382 to 192.168.6.89:6379
Moving 33 slots from 192.168.6.92:6382 to 192.168.6.89:6379
#############[root@***]
` actually, for totally balance, it should move 400 to echo new node which is four. i want to known it is same insufficient need to fix up or same other reason, or any suggest. therefore, we have many keys in cluster, about 120K per slot.
Comment From: bsergean
One problem seems to be that 192.168.6.92:6379 is unreachable.
Comment From: king526
One problem seems to be that 192.168.6.92:6379 is unreachable.
I am sorry that not the reason because full correctly cluster has same problem. the miss one is move to another cluster hardly to do some testing,i am sorry had this in the paste.
Comment From: bsergean
I wrote a resharding tool but it does not have a rebalancing option. Have you running redis-cluster in fix mode ?
On Jun 17, 2020, at 6:43 PM, king526 notifications@github.com wrote:
One problem seems to be that 192.168.6.92:6379 is unreachable.
I am sorry that not the reason because full correctly cluster has same problem. the miss one is move to another cluster hardly to do some testing,i am sorry had this in the paste.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/antirez/redis/issues/7405#issuecomment-645718106, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC2O6UIF5DFWS6V7RIMHWBDRXFWK3ANCNFSM4N7PZQ5A.