BUSYKEY: BUSYKEY Target key name already exists
RedisWhat does it mean?
RESTORE (or a similar command) failed because the target key already exists. By default Redis does not overwrite an existing key.
Why does it happen?
The key name being restored with RESTORE already exists in the database, previous data was not cleaned up, or multiple restore attempts to the same key.
How to fix it
If you want to overwrite the existing key, add the REPLACE option to RESTORE. Alternatively, delete the target key first (DEL mykey) or use a different key name. Check existence beforehand with EXISTS mykey.
More from this engine
- ERR value is not a valid floatERR value is not a valid float
- ERR increment or decrement would overflowERR increment or decrement would overflow
- ERR max number of clients reachedERR max number of clients reached
- ERR no such keyERR no such key
- ERR DUMP payload version or checksum are wrongERR DUMP payload version or checksum are wrong
- NOREPLICASNOREPLICAS Not enough good replicas to write
- ERR This instance has cluster support disabledERR This instance has cluster support disabled