Skip to main content
Use SCRIPT KILL to stop a running read-only script. Only a script that has not yet written anything can be killed: stopping one halfway through its writes would leave the dataset in a state that no atomic execution could produce, so Redis refuses and the server has to be restarted instead. This is the main reason to keep scripts short and to use EVAL_RO wherever a script only reads. The current Upstash deployment recognizes the command but has no interruptible running-script state to act on, so it replies with a NOTBUSY error.

Syntax

Arguments

This command takes no arguments.

Important points

  • The current deployment recognizes this command but reports NOTBUSY because it does not expose an interruptible running-script state.
  • As with Redis, a script that has already performed writes must not be killed because doing so would violate atomicity.

Response

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
This command is not supported yet in @upstash/redis.
This command is not supported yet in upstash_redis.