Actions
Bug #13582
closed
Hikari pool autocomit configuration is incorrect, which can impact performance
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
With Hicari in debug, we see a lot of:
[2018-09-26 16:58:58] DEBUG com.zaxxer.hikari.pool.PoolBase - HikariPool-1 - Reset (autoCommit) on connection org.postgresql.jdbc.PgConnection@275d4254 [2018-09-26 16:59:03] DEBUG com.zaxxer.hikari.pool.PoolBase - HikariPool-1 - Reset (autoCommit) on connection org.postgresql.jdbc.PgConnection@275d4254 [2018-09-26 16:59:03] DEBUG com.zaxxer.hikari.pool.PoolBase - HikariPool-1 - Reset (autoCommit) on connection org.postgresql.jdbc.PgConnection@275d4254
Which seems to mean that the pool is not correctly configured regarding autocommit, see: https://stackoverflow.com/questions/41202242/reset-autocommit-on-connection-in-hikaricp
Updated by François ARMAND about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2041
Updated by Vincent MEMBRÉ about 6 years ago
- Subject changed from Hikari pool autocomit is badly configured, which can impact performance to Hikari pool autocomit configuration is incorrect, which can impact performance
Updated by François ARMAND about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|2a48085fc59c8b15cf8988269840c434bcb2321e.
Updated by Vincent MEMBRÉ about 6 years ago
- Status changed from Pending release to Released
Updated by Nicolas CHARLES almost 6 years ago
- Related to Bug #14056: Cannot modify groups when workflow are enabled added
Actions