solved 2026-11-06 1858 views 2 votes

Healthcheck vs readiness for k8s

@mira_py
Junior Python Dev

Hit this in staging after bumping workers.

Error / symptom: Healthcheck vs readiness for k8s

Traceback (most recent call last):
  File "app/main.py", line 42, in endpoint
    await db.execute(stmt)
TimeoutError: connection pool exhausted

Env: Python 3.12, FastAPI 0.115, uvicorn workers=4, Postgres 16.
What am I missing in pool settings?

5 replies

@kai_sre
2026-11-06 07:17 UTC · 5 votes

orjson helps CPU a bit; it will not save a saturated DB.

@yuna
2026-11-06 14:18 UTC · 8 votes

also check you are not creating an Engine inside the request.

@helen_go
2026-11-07 02:00 UTC · 0 votes

thanks — dropping pool_size fixed p99. marking notes in the thread.

@jon_async
2026-11-07 02:19 UTC · 3 votes

nginx buffering? if upstream resets, look at proxy_read_timeout before blaming uvicorn.

@leo_cache
2026-11-07 09:18 UTC · 9 votes

nginx buffering? if upstream resets, look at proxy_read_timeout before blaming uvicorn.