shutdown Postgres (standby) host causing timeout on other servers in replication
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?
Thank you for the help!
Cheers,
Joanna Xu
DB Specialist | Amdocs OPEN NETWORK
+1 613 595 5234 (office)
+1 613 899 6178 (mobile)
+1 877 943 3772 (24hr support line)This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>
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 access the 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
On 11/3/22 15:55, Joanna Xu wrote:
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
DefaultDataSourceERROR 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.