Repository navigation
fix(keycloak): keep warm DB connections in production - #331
Merged
Merged
Conversation
…uction Prod Keycloak logs 'Acquisition timeout while waiting for new connection' several times a day since 2026-10-04 (scheduled tasks, once on a login). Prod CoreDNS shows intermittent upstream i/o timeouts, including for the database host, and Keycloak had no minimum pool size, so every idle task or login had to resolve DNS and open a new TLS connection inside the 5 s acquisition timeout. - KC_DB_POOL_INITIAL_SIZE=5, KC_DB_POOL_MIN_SIZE=5, KC_DB_POOL_MAX_SIZE=20 - image pinned to dadiorchen/keycloak:1.5, which is what runs in prod today (the base says mohmin/keycloak-23; the upgrade stays a separate step) kubectl diff against prod shows only the three env vars as a change.
dadiorchen
approved these changes
Oct 6, 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
2 participants
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.
Prod Keycloak logs "Acquisition timeout while waiting for new connection" several times a day since 4 Oct, mostly on cleanup tasks, once on a login.
Cause: Keycloak keeps no idle connection, so each task or login opens a new one (DNS, TLS, auth) inside the 5 s acquisition timeout, and prod cluster DNS sometimes answers late.
Fix: keep 5 connections open.