Quick answer
Redis documents reserved descriptors as maxclients plus 32 file descriptors. Redis reserves descriptors for internal use when determining effective client capacity.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| reserved descriptorsRedis reserves descriptors for internal use when determining effective client capacity. | maxclients plus 32 file descriptors | Redis server | RedisAug 22, 2026 |
Why does this limit matter?
An OS limit equal to maxclients is still too small for the configured client target.
This value is scoped to Redis server; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Set and verify the process soft limit above maxclients + 32 and inspect startup logs.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Cluster bus, replicas, monitoring, and managed-provider policies can alter real socket usage.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related