Skip to content

Warn instead of raising when the connection pool is smaller than the thread pool#752

Closed
ajaynomics wants to merge 1 commit into
rails:mainfrom
ajaynomics:fix/736-pool-size-warning
Closed

Warn instead of raising when the connection pool is smaller than the thread pool#752
ajaynomics wants to merge 1 commit into
rails:mainfrom
ajaynomics:fix/736-pool-size-warning

Conversation

@ajaynomics

Copy link
Copy Markdown

Solid Queue currently refuses to boot when the Active Record connection pool is smaller than the worker thread pool, raising a configuration validation error. This blocks legitimate setups such as I/O-bound queues that run many threads against a deliberately small pool.

This downgrades the check from a validation error to a SolidQueue.logger warning. The warning is emitted once on the boot path in Supervisor.start, after the configuration is confirmed valid, so undersized configurations boot and run while still surfacing the advisory. Configuration#valid? stays purely about whether we can boot.

The original message wording is retained, just at warn level.

Closes #736

…thread pool

Solid Queue refused to boot when the Active Record connection pool was
smaller than the worker thread pool. This blocked legitimate setups, such
as I/O-bound queues that run many threads against a deliberately small pool.

Per the discussion in rails#736, downgrade the check from a validation error to
a SolidQueue.logger warning emitted once on the boot path in
Supervisor.start, so undersized configurations boot while still surfacing
the advisory. valid? stays purely about whether we can boot.

Closes rails#736
@ajaynomics ajaynomics closed this Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

There should be a way to bypass the connection pool vs worker threads check

1 participant