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

From Tom Lane
Subject Re: shutdown Postgres (standby) host causing timeout on other servers in replication
Date
Msg-id 2188169.1667515780@sss.pgh.pa.us
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
Joanna Xu <Joanna.Xu@amdocs.com> writes:
> 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
accessthe database due to the timeout. 
> DAO-00002 datasource connection failure:Time out waiting for a DefaultDataSource
> ERROR SQLException code: 0 SQLState: null

There's no such error message, indeed nothing about "DefaultDataSource"
at all, in the community Postgres code.  I guess it's coming from some
extension or maybe some client-side replication logic.  I suggest
finding where it's coming from and then asking the appropriate authors.

            regards, tom lane



pgsql-general by date:

Previous
From: Adrian Klaver
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: "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"