Pain point · Reliability & bugs · Causes churn
Server stuck in a loop failing to reach Postgres, workflows stall
2 source threads · first seen 2023-10 · last seen 2024-09
Summary
On a self-hosted ARM64 cluster against RDS Postgres, the history service loops on a database connection error and workflows stop progressing, with no known reproduction.
- Affects
- Self-hosters on AWS RDS Postgres
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Workflows are stuck and the server logs indicate the history service is stuck in a loop trying to connect to a Postgres 14.12 DB”
“50% of all CPU load (4 cores) just from opening new connections”