127.0.0.1:6379> scan 10 1) "25165834" 2) 1) "ac:462262851295219346089:$h" 2) "ac:73244725777718607779631:$h" 3) "ac:49736152545177773847163:$h" 4) "ac:6977706739628641233132:$h" 5) "ac:4613325082181445689196:$h" 6) "ac:786490290122956665225135:$h" 7) "ac:79182828723706138306336:$h" 8) "ac:722817271722227621783437:$h" 9) "ac:74772312392728607323065:$h" 10) "ac:70052316129801965935959:$h" 127.0.0.1:16028> hgetall "ac:462262851295219346089:$h" (error) MOVED 10455 10.123.123.12:6379

I want to delete the key to free up space, and scan it . When reading the key, an error of move. is reported. Then I went to the move node and prompted that the key does not exist. After I migrated all the slots on this node, the info keyspace of this node still has many keys. flushall can free up space, why? Is there a way to handle this situation

Comment From: 553589912

https://github.com/redis/redis/issues/4810 和这个问题类似

Comment From: DriverX

I found intresting command in redis-cli cluster management - --cluster-search-multiple-owners. Introduced in https://github.com/redis/redis/pull/5681