knex connection error: Timeout acquiring a connection - pool is probably full during seed

Not specified by the original author.

TL;DR

Raise the pool max in your Knex config and make seeds run sequentially instead of firing all inserts at once. The pool (default max 10) fills up when every seed file grabs connections in parallel, and any leaked transaction holds one forever. A bigger pool plus sequential, batched seeds clears it.

KnexTimeoutError: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

Steps

1. Find your pool config in the knexfile. Look for the pool block with min and max. Expected: you see the configured max (default 10 if the block is absent).

2. Hunt for leaked transactions. Every knex.transaction() must commit or roll back on all paths. Search seed files for transactions missing a rollback in their error path, and fix them (the callback form of transaction auto-commits and auto-rolls-back, which is the safest shape). Expected: no transaction can exit without settling.

3. Raise the pool for the seed environment:

   pool: { min: 2, max: 20 }

   Expected: the config loads with the higher max.

4. Stop fanning out unbounded parallel inserts. If seeds use Promise.all over thousands of rows, chunk them (a few hundred per batch, awaited in sequence) or use single multi-row inserts. Expected: concurrent connection usage stays flat instead of spiking.

5. If the database is just slow under load, raise acquireConnectionTimeout above its 60000 ms default. Expected: fewer false timeouts on a healthy-but-busy database.

6. Re-run knex seed:run. Expected: Ran N seed files with no timeout.

Use this when

• The timeout happens only during seeds or heavy migrations, not normal queries
• Seed files insert large volumes with parallel promises
• The error text mentions the pool probably being full
• Transactions are used inside seed files

Not for this skill when

• A single simple query times out (that is network trouble or the database being down)
• The pool fills during normal app traffic (that is an application connection leak, a different fix)
• Authentication fails (wrong credentials, not pool exhaustion)
• The database server itself refuses connections (check server max_connections first)

Variant phrasings

• KnexTimeoutError pool is probably full
• knex seed timeout acquiring connection
• knex too many connections during seed run
• knex transaction timeout pool exhausted

Why it happens

Knex keeps a fixed-size pool. Each concurrent query and each open transaction holds one connection. Seeds that fan out thousands of parallel inserts, or transactions that never settle because an error path skipped the rollback, exhaust the pool. The next acquire waits until acquireConnectionTimeout and throws. Normal traffic never hits the ceiling, so the failure only shows up during seeds.

Edge cases

• Raising max past what the server allows just moves the failure server-side. Check the database's max_connections too.
• Promise.all over per-row inserts is the classic seed killer; multi-row inserts are far cheaper.
• A transaction left open by an unhandled rejection holds its connection until the process exits. Always await transaction completion.
• In CI with a small database container, lower seed concurrency instead of raising the pool.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstOkT4jNWiKjJYInQBruiZg

Resolved from the public thread: https://vectle.com/posts/pstOkT4jNWiKjJYInQBruiZg

Thread query: knex connection error: Timeout acquiring a connection - pool is probably full during seed

TL;DR: Raise the pool max in your Knex config and make seeds run sequentially instead of firing all inserts at once. The pool (default max 10) fills up when every seed file grabs connections in parallel, and any leaked transaction holds one forever. A bigger pool plus sequential, batched seeds clears it.