kunal
CDCloudflare Developers
•Created by kunal on 3/18/2025 in #hyperdrive
Our Cloudflare Worker (backed by
do you have a connection timeout configured for your database driverGot it, thanks. Excited for the visibility work! On the connection timeout - Is this on the level of Postgres (like statement_timeout), or the client side library (we use the Node library 'pg')?
11 replies
CDCloudflare Developers
•Created by kunal on 3/18/2025 in #hyperdrive
Our Cloudflare Worker (backed by
Two observations from our side:
1. The high wall time spikes seems to correlate to Hyperdrive issues. We saw the same spike on Saturday when us-east-1 databases were broken from Hyperdrive. On that incident, we didn't see any changes in the Hyperdrive metrics (latency or error rate) but of course saw a lot of errors and walltime spikes
2. These client disconnect errors that we see what Hyperdrive fails don't trigger our Sentry alerts. I'm not sure why - it could be that the way that error presents itself, our in-worker Sentry integration doesn't trigger or doesn't get a chance to drain
11 replies
CDCloudflare Developers
•Created by kunal on 3/18/2025 in #hyperdrive
Our Cloudflare Worker (backed by
One other thing I just enabled to try to see if I could get out of these infinite timeouts is setting a Postgres statement timeout:
ALTER ROLE <role> SET statement_timeout='10s';
Though I think it will only kick in on new connections, not sure how often the connections are refreshed
11 replies
CDCloudflare Developers
•Created by kunal on 3/18/2025 in #hyperdrive
Our Cloudflare Worker (backed by
In case it's useful:
- Account ID: cf4bd8e45a557fecf50a1b2af74b8453
- Worker name: spindl-adserver
- Hyperdrives: 5dbce450a32a4279a8cdf3a8596ee308, 4d4fe23ab437464f86f59bb8ed897e88, dc0758eacd8945a4b2bea40cb1654223
11 replies
CDCloudflare Developers
•Created by kunal on 3/18/2025 in #hyperdrive
Our Cloudflare Worker (backed by
11 replies