| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: shutdown Postgres (standby) host causing timeout on other servers in replication |
| Date: | 2022-11-04 01:46:48 |
| Message-ID: | aa41e570-7740-2be5-8205-0ff5a3d60c0b@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2022-11-04 01:50:25 | 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" |
| Previous Message | Peter J. Holzer | 2022-11-03 23:01:02 | 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" |