Jira (PDB-4555) PuppetDB connection failure causing shutdown

[Austin Blatt (JIRA)]

Austin Blatt created an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Issue Type: Improvement Assignee: Austin Blatt Created: 2019/10/22 10:41 AM Priority: Normal Reporter: Austin Blatt Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown

Change By: Austin Blatt I believe this was introduced by [this query|https://github.com/puppetlabs/puppetdb/pull/3097/files#diff-66cce979c7939fbe2d11a146eae980ccR397] to Postgres that happens outside the "try again" loop for database migrations. If it fails to get a database connection, it will bring the whole PuppetDB down unlike the migrations which allowed PuppetDB to try again.

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown

Change By: Austin Blatt Fix Version/s: PDB 5.2.11 Fix Version/s: PDB 6.7.2 Fix Version/s: PDB 6.3.6

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt

I believe this PuppetDB _requires_ Postgres to be started before PuppetDB, otherwise its first connection to the database will fail, causing PuppetDB to throw and error and shutdown with the following message {code} ERROR [p.t.internal] Error during service start!!! java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3011ms. {code} Previously, if postgresql was not up, PuppetDB would retry the connection with the message {code} ERROR [p.p.c.services] Will retry database connection after temporary failure: java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3008ms. {code} This was introduced by [this query|https://github.com/puppetlabs/puppetdb/pull/3097/files#diff-66cce979c7939fbe2d11a146eae980ccR397] to Postgres that happens outside the "try again" loop for database migrations. If it fails to get a database connection , it will bring the whole PuppetDB down unlike the migrations which allowed PuppetDB to try again failures .

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown Change By: Austin Blatt

PuppetDB _requires_ Postgres to be started before PuppetDB, otherwise its first connection to the database will fail, causing PuppetDB to throw and error and shutdown with the following message {code} ERROR [p.t.internal] Error during service start!!! java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3011ms. {code}

Previously, if postgresql was not up running , PuppetDB would retry the connection with the message

{code} ERROR [p.p.c.services] Will retry database connection after temporary failure: java.sql.SQLTransientConnectionException: PDBMigrationsPool - Connection is not available, request timed out after 3008ms. {code}

This was introduced by [this query|https://github.com/puppetlabs/puppetdb/pull/3097/files#diff-66cce979c7939fbe2d11a146eae980ccR397] to Postgres that happens outside the "try again" loop for database connection failures.

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555

PuppetDB connection failure causing shutdown

Change By: Austin Blatt Issue Type: Improvement Bug

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown

Change By: Austin Blatt Affects Version/s: PDB 5.2.10 Affects Version/s: PDB 6.3.5 Affects Version/s: PDB 6.7.1

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown

Change By: Austin Blatt Acceptance Criteria: PuppetDB does not crash on startup when Postgres is not available and will retry the connection until a successful connection is made

Add Comment

[Austin Blatt (JIRA)]

Austin Blatt updated an issue

PuppetDB / PDB-4555 PuppetDB connection failure causing shutdown

Change By: Austin Blatt Release Notes Summary: PDB-4509 introduced a regression where PuppetDB would attempt to make an initial database connection, if this failed, it would shutdown. Now PuppetDB will retry the database connection as before. Release Notes: Bug Fix

Add Comment