check proxy_read_timeout before blaming uvicorn resets.
Readiness probe that does not DDoS itself
@jon_async
Senior Python Dev
Hit this after a routine bump.
Symptom: Readiness probe that does not DDoS itself
TimeoutError / pool exhausted / upstream reset
(versions in next reply if needed)
Env: Python 3.12, FastAPI recent, uvicorn workers≥2.
What should I check first?
9 replies
@cleo_dev29
2026-11-10 05:16 UTC · 6 votes
@sana
2026-11-10 14:11 UTC · 3 votes
paste engine kwargs and max_connections. worker×pool is the usual culprit.
@tara
2026-11-11 02:45 UTC · 5 votes
minimal repro with ASGITransport would help more than screenshots.
@brick
2026-11-11 10:05 UTC · 5 votes
close the client in lifespan shutdown; leaks show up after a day of traffic.
@elias
2026-11-11 13:42 UTC · 9 votes
I would put rate limits at the edge and keep app middleware as a second line.
@leda
2026-11-12 08:22 UTC · 1 votes
that traceback looks like Engine created per request — move it to lifespan.
@nox
2026-11-13 04:12 UTC · 2 votes
check proxy_read_timeout before blaming uvicorn resets.
@gabe
2026-11-13 17:01 UTC · 5 votes
dropping pool_size per worker fixed it for us on the same box size.
@rina_lab79
2026-11-13 23:00 UTC · 7 votes
check proxy_read_timeout before blaming uvicorn resets.