Fixes #39090 - configure DB connections and timeout#63
Merged
ianballou merged 1 commit intoKatello:mainfrom Feb 23, 2026
Merged
Fixes #39090 - configure DB connections and timeout#63ianballou merged 1 commit intoKatello:mainfrom
ianballou merged 1 commit intoKatello:mainfrom
Conversation
9a179ec to
f73837b
Compare
f73837b to
3ba5b82
Compare
sjha4
reviewed
Feb 23, 2026
sjha4
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Allows users to configure the maximum number of DB connections and the connect timeout.
Since the smart-proxy uses WEBrick instead of Puma, we can't use the same worker-related logic that Foreman has with determining the amount of DB connections to allow. So, I am bumping up the default from 4 to 30 and allowing users to configure it themselves. We will need Installer support for this too. I am also bumping the timeout up to 30 seconds based on some quick research and a user report that this helped with concurrent container pulls.