Re: shutdown Postgres (standby) host causing timeout on other servers in replication - Mailing list pgsql-general

From Ron
Subject Re: shutdown Postgres (standby) host causing timeout on other servers in replication
Date
Msg-id aa41e570-7740-2be5-8205-0ff5a3d60c0b@gmail.com
Whole thread Raw
In response to shutdown Postgres (standby) host causing timeout on other servers in replication  (Joanna Xu <Joanna.Xu@amdocs.com>)
List pgsql-general
On 11/3/22 15:55, Joanna Xu wrote:
@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;}span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;}div.WordSection1 {page:WordSection1;}

Hi All,

 

We have PostgreSQL master-slave replication configuration with 4 servers. 

After shutting down one standby server, we found below errors on all other 3 servers and the applications couldn’t access the database due to the timeout.

DAO-00002 datasource connection failure:Time out waiting for a DefaultDataSource

ERROR SQLException code: 0 SQLState: null

 

What could be the cause of the errors?  Would anyting be helpful to prevent it from happening?


Synchronous or asynchronous replication?

Go to the database server and look in it's logs.

--
Angular momentum makes the world go 'round.

pgsql-general by date:

Previous
From: "Peter J. Holzer"
Date:
Subject: Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"
Next
From: Bryn Llewellyn
Date:
Subject: Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"