docker image redis:5.0-rc

>>> Importing data from redis:6379 to cluster redis-3:6379
>>> Performing Cluster Check (using node redis-3:6379)
S: f03d7d68325c04f55862229ffa579fbc3ba7e5af redis-3:6379
   slots: (0 slots) slave
   replicates e0cd0bba3b673316aadc18e63239a7eed08d31fa
S: 3d527ed762d691fa04fb3bf7e6e1ea145b1bbcfc 10.1.1.97:6379
   slots: (0 slots) slave
   replicates 374029a04dcbe0691eaf7334d876605646eb5795
S: bc41b4a9b5722483e0337919ca54bdc67c77d5fd 10.1.1.99:6379
   slots: (0 slots) slave
   replicates fb5c8f0413849afd45a3d0216d9e0119435571ce
M: e0cd0bba3b673316aadc18e63239a7eed08d31fa 10.1.1.94:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: fb5c8f0413849afd45a3d0216d9e0119435571ce 10.1.1.96:6379
   slots:[10923-16383] (5461 slots) master
   1 additional replica(s)
M: 374029a04dcbe0691eaf7334d876605646eb5795 10.1.1.95:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
*** Importing 1 keys from DB 0
Migrating key to 10.1.1.96:6379: Source redis:6379 replied with error:
ERR Target instance replied with error: BUSYKEY Target key name already exists.

Couldn't find documentation on --cluster-replace / --cluster-copy but it seems it's not working?

Comment From: antirez

CC @artix75

Comment From: artix75

@gertcuykens The syntax is:

redis-cli --cluster import $M:6379 --cluster-from redis:6379 --cluster-replace --cluster-copy

Without slash ('/').

I've tried and it works using the --cluster-replace option.

Comment From: gertcuykens

Thx for looking into it but just a sec because by '/' i meant that I tried first replace and then copy but they both gave the same error message above. So to make it more clear

Step 1) This should always give you the error message before you even try step 2 ERR Target instance replied with error: BUSYKEY Target key name already exists.

redis-cli --cluster import $M:6379 --cluster-from redis:6379

Step 2) Once and only once you get that error message above you try to fix it by using and verify it did the replace the value of a already existing key you want to import

redis-cli --cluster import $M:6379 --cluster-from redis:6379 --cluster-replace

Step 3) This should also solve the error message above but can't find the documentation to tell me what the name of the copy would be?

redis-cli --cluster import $M:6379 --cluster-from redis:6379 --cluster-copy

Note that I didn't try to use them both at the same time, If that's the case that it only works when doing it this way then this should be definitely be documented because it's counter intuitive for me?

redis-cli --cluster import $M:6379 --cluster-from redis:6379 --cluster-replace --cluster-copy

Comment From: huangzhw

I think it was fixed by https://github.com/redis/redis/pull/8945

Comment From: oranagra

I agree.. If i understand the report correctly, the complaint is that when --cluster-replace is used without --cluster-copy it doesn't work.. please respond if that's not the case. thanks.