Project

General

Profile

Bug #13582

Hikari pool autocomit configuration is incorrect, which can impact performance

Added by François ARMAND 3 months ago. Updated about 2 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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

Associated revisions

Revision 2a48085f (diff)
Added by François ARMAND 3 months ago

Fixes #13582: Hikari pool autocomit is badly configured, which can impact performance

History

#1 Updated by François ARMAND 3 months 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

#2 Updated by Vincent MEMBRÉ 3 months 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

#3 Updated by François ARMAND 3 months ago

  • Status changed from Pending technical review to Pending release

#4 Updated by Vincent MEMBRÉ about 2 months ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.15, 4.3.5 and 5.0.1 which were released today.
Changelog
Changelog
Changelog

Also available in: Atom PDF