BUSYKEY error
RESTORE tried to create a key that already exists.
Redis returns this error when RESTORE would create a key that already exists. RESTORE creates a key from a value that DUMP serialized. By default, it doesn't overwrite an existing key.
BUSYKEY Target key name already exists.
In client libraries
| Client library | Exception or error type | Message |
|---|---|---|
| redis-py | ResponseError |
BUSYKEY Target key name already exists. |
| Jedis | JedisDataException |
BUSYKEY Target key name already exists. |
| node-redis | SimpleErrorTest with err.message.startsWith('BUSYKEY') |
BUSYKEY Target key name already exists. |
| Lettuce The async API wraps the exception in an ExecutionException (get()) or a CompletionException (join()). |
RedisBusyException |
BUSYKEY Target key name already exists. |
| go-redis | redis.ErrorTest with redis.HasErrorPrefix(err, "BUSYKEY") |
BUSYKEY Target key name already exists. |
| ioredis | ReplyErrorTest with err.message.startsWith('BUSYKEY') |
BUSYKEY Target key name already exists. |
| StackExchange.Redis NRedisStack uses StackExchange.Redis, so it raises the same exceptions. The sync and async APIs raise the same exceptions. |
RedisServerException |
BUSYKEY Target key name already exists. |
| Predis | Predis\Response\ServerExceptionTest with $e->getErrorType() === 'BUSYKEY' |
BUSYKEY Target key name already exists. |
| redis-rb | Redis::CommandError |
BUSYKEY Target key name already exists. (redis://<host>:<port>) |
| redis-rs The sync and async APIs raise the same errors. |
ErrorKind::ExtensionTest with err.code() == Some("BUSYKEY") |
"BUSYKEY": Target key name already exists. |
Example
> SET mykey "value"
OK
> RESTORE mykey 0 "<serialized-value>"
(error) BUSYKEY Target key name already exists.
How to fix it
- To replace the existing key, add the
REPLACEoption:RESTORE mykey 0 "<serialized-value>" REPLACE. - To keep the existing key, restore the value under a different key name.
MIGRATE, which moves keys to another Redis server, also has a REPLACE option for keys that already exist on the target server.