HikariCP pool sizing for elastic cloud deployments in JHipster
0 reputation · 03 Sept 2020, 12:09 UTC
Connection Pool Configuration in Elastic Environments
JHipster leverages HikariCP as the default connection pool provider, integrating closely with Spring Boot's externalized configuration. In highly elastic cloud environments, the application must balance rapid scaling of container instances against the fixed connection limits of the underlying database.
Current configurations often rely on a static maximumPoolSize and minimumIdle. However, when instances scale rapidly, a high minimumIdle across many pods can lead to database-side resource exhaustion, while a too-low limit may cause request queuing during traffic spikes.
Given the transition toward Spring Boot 3.x standards, there is uncertainty regarding the optimal relationship between these two properties to maintain stability during aggressive auto-scaling events.
- What is the recommended ratio between
minimumIdleandmaximumPoolSizefor JHipster applications deployed in elastic clusters? - How does the
leak-detection-thresholdinteract with these settings to prevent false positives during high-latency scaling events?
jhipster