NOTBUSY No scripts in execution right now: No scripts in execution right now
RedisWhat does it mean?
You sent SCRIPT KILL or FUNCTION KILL, but no Lua script/function is currently running (and killable). The command was rejected because there is nothing to terminate.
Why does it happen?
The script had already finished by the time you tried to stop it; SCRIPT KILL was sent to the wrong node (while the script runs on another instance); or the BUSY condition resolved on its own before SCRIPT KILL. Usually a timing issue.
How to fix it
If no script is actually stuck, there is nothing to do; this is a safe/informational reply. If you get a BUSY error (a script exceeded busy-reply-threshold, named lua-time-limit before Redis 7), try SCRIPT KILL (FUNCTION KILL for functions) on the correct node where the script is running. If the script has modified data, SCRIPT KILL does not work; as a last resort SHUTDOWN NOSAVE may be needed. Break long scripts into pieces and respect the time limit.
More from this engine
- ERR DISCARD without MULTIDISCARD without MULTI
- BUSYGROUP Consumer Group name already existsConsumer group already exists
- NOGROUP No such key or consumer groupNo such key or consumer group in stream
- DENIED Redis is running in protected modeRedis is running in protected mode
- ERR Can't execute '<cmd>': only (P|S)SUBSCRIBE / (P|S)UNSUBSCRIBE / PING / QUIT / RESET are allowed in this contextCommand not allowed in subscribe context
- ERR SELECT is not allowed in cluster modeSELECT is not allowed in cluster mode
- ERR wrong number of arguments for commandWrong number of arguments for command