Skip to content

Commit 649dee3

Browse files
Update troubleshooting.mdx
1 parent f836b21 commit 649dee3

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/content/docs/hyperdrive/observability/troubleshooting.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,7 @@ Hyperdrive may also encounter `ErrorResponse` wire protocol messages sent by you
4242
| `Internal error.` | Something is broken on our side. | Check for an ongoing incident affecting Hyperdrive, and contact Cloudflare Support. |
4343
| `Failed to acquire a connection from the pool.` | Hyperdrive timed out while waiting for a connection to your database, or cannot connect at all. | If you are seeing this error intermittently, your Hyperdrive pool is being exhausted because too many connections are being held open for too long by your worker. This can be caused by a myriad of different issues, but long-running queries/transactions are a common offender. |
4444
| `Server connection attempt failed: connection_refused` | Hyperdrive is unable to create new connections to your origin database. | A network firewall or access control list (ACL) is likely rejecting requests from Hyperdrive. Ensure you have allowed connections from the public Internet. Sometimes, this can be caused by your database host provider refusing incoming connections when you go over your connection limit. |
45+
46+
### Improving performance
47+
48+
Having query traffic written as transactions can limit performance. The reason for this is because in the case of a transaction the connection must be held for the duration of the transaction which limits connection multiplexing. If there are mulitple queries per transaction this can be particularly impactful on connection multiplexing. Where possible we recommend not wrapping queries in transactions to allow the connections to be shared more aggressively.

0 commit comments

Comments
 (0)