Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-3195

Investigate "Reset (nothing) on connection"

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 5.1.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Data Platform
    • Story Points:
      1
    • Sprint:
      Data Platform 2017-08-09
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      PuppetDB no longer sends redundant "SET TRANSACTION READ COMMITTED" commands to the database.

      Description

      I'm looking through some user logs. At the DEBUG level they contain this lines several times a second, and often 20-30 times/sec

      2016-11-03 00:00:02,431 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b                                     2016-11-03 00:00:02,433 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6f86217a                                    
      2016-11-03 00:00:02,440 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b                                     2016-11-03 00:00:02,444 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6f86217a                                    
      2016-11-03 00:00:02,451 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@14929bf6                                    2016-11-03 00:00:02,454 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@144a14                                      
      2016-11-03 00:00:02,469 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b                                     2016-11-03 00:00:02,478 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@2fb3df1d                                    
      2016-11-03 00:00:02,478 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b                                     2016-11-03 00:00:02,487 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@144a14                                      
      2016-11-03 00:00:02,487 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b                                     2016-11-03 00:00:02,496 DEBUG [c.z.h.p.PoolBase] PDBReadPool - Reset (nothing) on connection org.postgresql.jdbc.PgConnection@6ca024b
      

      Reading https://github.com/brettwooldridge/HikariCP/issues/436, the author seems to indicate that this implies wasted network overhead for some databases but not others. We should figure out what it means for postgres, and if it is actually resulting in chatter, try to cut it out.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                russell.mull Russell Mull
                Reporter:
                wyatt Wyatt Alt
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support