# ERR: Command queue full for client, dropping connection

- **ID:** `redis/command-queue-full`
- **Domain:** redis
- **Category:** resource_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

A client's command buffer exceeded the client-output-buffer-limit, causing Redis to disconnect it to prevent memory exhaustion.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Redis 6.2 | active | — | — |
| Redis 7.0 | active | — | — |
| Redis 7.2 | active | — | — |

## Workarounds

1. **Check the client's application logic: use pipelining or batching to reduce the number of commands sent per connection. Example: in Python, use redis-py pipeline.** (80% success)
   ```
   Check the client's application logic: use pipelining or batching to reduce the number of commands sent per connection. Example: in Python, use redis-py pipeline.
   ```
2. **Monitor slow consumers with CLIENT LIST and consider increasing client-output-buffer-limit for specific client types: CONFIG SET client-output-buffer-limit 'normal 0 0 0' (reset to default).** (70% success)
   ```
   Monitor slow consumers with CLIENT LIST and consider increasing client-output-buffer-limit for specific client types: CONFIG SET client-output-buffer-limit 'normal 0 0 0' (reset to default).
   ```

## Dead Ends

- **Increase client-output-buffer-limit to a very high value (e.g., 1GB)** — May hide the underlying issue (e.g., slow consumer or large replies) and risk OOM on Redis server. (45% fail)
- **Restart Redis server to clear all client connections** — Temporary fix; the issue will recur if the client behavior isn't changed. (60% fail)