| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joanna Xu <Joanna(dot)Xu(at)amdocs(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "Sandeep Yadav (93247)" <Sandeep(dot)Yadav2(at)amdocs(dot)com>, Sylwester Czerniewicz <Sylwester(dot)Czerniewicz(at)amdocs(dot)com> |
| Subject: | Re: shutdown Postgres (standby) host causing timeout on other servers in replication |
| Date: | 2022-11-03 22:49:40 |
| Message-ID: | 2188169.1667515780@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joanna Xu <Joanna(dot)Xu(at)amdocs(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next 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" |
| Previous Message | Adrian Klaver | 2022-11-03 22:37:07 | 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" |