Skip to content

Commit f0d12ff

Browse files
Document RPC timeouts in Redis config (TraceMachina#2168)
1 parent 2650680 commit f0d12ff

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

web/platform/src/content/docs/docs/config/production-config.mdx

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -525,3 +525,25 @@ Setting it to `-1` turns off the logging entirely.
525525
526526
You won't see those worker matching logs anymore. If you need to debug why actions aren't getting assigned to workers, you'll have to turn this back on temporarily or look at other metrics.
527527
For most production setups at scale, that's a fair trade-off for better Redis performance.
528+
529+
## RPC Timeouts and Back Pressure
530+
531+
Timeouts and concurrency limits help keep upstream RPC requests from piling up and
532+
stalling the system. These are especially important for Redis-backed stores.
533+
534+
### Redis Store Timeouts
535+
536+
Use `command_timeout_ms` and `connection_timeout_ms` to bound slow or stuck
537+
requests and trigger reconnects:
538+
539+
```json
540+
"redis_store": {
541+
"addresses": ["${REDIS_STORE_URL:-redis://redis-headless:6379}"],
542+
"command_timeout_ms": 10000,
543+
"connection_timeout_ms": 3000,
544+
"max_client_permits": 500
545+
}
546+
```
547+
548+
`max_client_permits` caps simultaneous in-flight requests to Redis, which can
549+
prevent timeouts and reduce pressure during spikes.

0 commit comments

Comments
 (0)