Redis Iris

Redis install Data types

Tools Community Docs

Login Sign up

Develop with Redis Libraries and tools Redis products

Commands

Download documentation

Choose the products and versions you want. Everything arrives as one .tar.gz, with a directory per product.

Format

This page

	Products	Version
	Develop with Redis Clients, data types, programmability, and Redis for AI. RedisVL is listed separately.
	Libraries and tools Client libraries, observability, and cloud integrations. Redis Data Integration is listed separately.
	RedisVL
	Redis Software
	Redis Cloud
	Redis for Kubernetes
	Redis Open Source
	Redis Iris context engine
	Redis Feature Form
	Redis Insight
	Redis Data Integration
	Glossary
	Command reference

FUNCTION KILL

Syntax text Syntax diagram API methods

FUNCTION KILL

Client:

function_kill() → Union[Awaitable[str], str]  // Status response

Possible errors

BUSY: ResponseError

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

functionKill() → SimpleStringReply  // Status response

Possible errors

BUSY: SimpleError (test with err.message.startsWith('BUSY'))

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

functionKill() → String  // Status response

Possible errors

BUSY: JedisBusyException

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

functionKill() → String  // Status response

Possible errors

BUSY: RedisBusyException

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

functionKill() → RedisFuture<String>  // Status response

Possible errors

BUSY: RedisBusyException

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

functionKill() → Mono<String>  // Status response

Possible errors

BUSY: RedisBusyException

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

FunctionKill(
    ctx: context.Context  // Context for the operation
) → *StringCmd  // Status response

Possible errors

BUSY: redis.Error (test with redis.HasErrorPrefix(err, "BUSY"))

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

kill() → Status

Possible errors

BUSY: Predis\Response\ServerException (test with $e->getErrorType() === 'BUSY')

See Redis error messages for what each error means. Other errors, such as connection errors, aren't listed.

Available since:: Redis Open Source 7.0.0
Time complexity:: O(1)
ACL categories:: @slow, @scripting,
Compatibility:: Redis Software and Redis Cloud compatibility

Kill a function that is currently executing.

The FUNCTION KILL command can be used only on functions that did not modify the dataset during their execution (since stopping a read-only function does not violate the scripting engine's guaranteed atomicity).

For more information please refer to Introduction to Redis Functions.

Redis Software and Redis Cloud compatibility

Redis Software	Redis Cloud	Notes
✅ Standard ✅ Active-Active	✅ Standard ✅ Active-Active

Return information

RESP2 RESP3

Simple string reply: OK.

Simple string reply: OK.