Обсуждение: shutdown Postgres (standby) host causing timeout on other servers in replication

Поиск
Список
Период
Сортировка

shutdown Postgres (standby) host causing timeout on other servers in replication

От
Joanna Xu
Дата:

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

Re: shutdown Postgres (standby) host causing timeout on other servers in replication

От
Tom Lane
Дата:
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



Re: shutdown Postgres (standby) host causing timeout on other servers in replication

От
Ron
Дата:
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.