database resource_error ai_generated partial

redis.exceptions.ResponseError: ERR command queue is full

ID: database/redis-command-queue-full

Also available as: JSON · Markdown · 中文

80%Fix Rate

83%Confidence

1Evidence

2024-02-14First Seen

Version Compatibility

Version	Status	Introduced	Deprecated	Notes
Redis 6.2	active	—	—	—
Redis 7.0	active	—	—	—
Redis 7.2	active	—	—	—

Root Cause

The Redis server's command queue has reached its maximum capacity (controlled by client-output-buffer-limit), causing new commands from the client to be rejected.

generic

中文

Redis 服务器的命令队列已达到最大容量（由 client-output-buffer-limit 控制），导致来自客户端的新命令被拒绝。

Official Documentation

https://redis.io/docs/latest/develop/reference/clients/

Workarounds

85% success Increase the client output buffer limit for the relevant client type (e.g., normal) in redis.conf: client-output-buffer-limit normal 0 0 0 Then restart Redis or send CONFIG SET command.
```
Increase the client output buffer limit for the relevant client type (e.g., normal) in redis.conf:
client-output-buffer-limit normal 0 0 0
Then restart Redis or send CONFIG SET command.
```
75% success Reduce the number of pipelined commands sent by the client, or batch them more efficiently to prevent queue buildup.
```
Reduce the number of pipelined commands sent by the client, or batch them more efficiently to prevent queue buildup.
```

中文步骤

Increase the client output buffer limit for the relevant client type (e.g., normal) in redis.conf:
client-output-buffer-limit normal 0 0 0
Then restart Redis or send CONFIG SET command.

Reduce the number of pipelined commands sent by the client, or batch them more efficiently to prevent queue buildup.

Dead Ends

Common approaches that don't work:

Restarting the Redis server without changing buffer limits 90% fail
The queue resets temporarily but fills up again under the same load; the error returns.
Increasing maxmemory to allow more memory 85% fail
maxmemory does not affect command queue limits; it controls total memory usage.