pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedLogical wal receiver (background worker) not detecting when publisher node has died
3+ messages / 2 participants
[nested] [flat]
* Logical wal receiver (background worker) not detecting when publisher node has died
@ 2018-11-23 05:20 Achilleas Mantzios <achill@matrix.gatewaynet.com>
2018-11-24 01:00 ` Re: Logical wal receiver (background worker) not detecting when publisher node has died Rui DeSousa <rui@crazybean.net>
0 siblings, 1 reply; 3+ messages in thread
From: Achilleas Mantzios @ 2018-11-23 05:20 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Dear List,
Coming back from :
https://www.postgresql.org/message-id/ae8812c3-d138-73b7-537a-a273e15ef6e1%40matrix.gatewaynet.com
and having got absolutely no helpful answer from our infrastructure
people, I would like to ask :
Is it on earth possible that the primary (publisher node) has crushed
while on the subscriber node the logical wal receiver goes on happily
like there is no problem at all, no messages in log, no timeouts, acts
if nothing happen ?
(in the meantime the second standby instantly detected the crush of the
primary and immediately restarted re-connection attempts)
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Logical wal receiver (background worker) not detecting when publisher node has died
2018-11-23 05:20 Logical wal receiver (background worker) not detecting when publisher node has died Achilleas Mantzios <achill@matrix.gatewaynet.com>
@ 2018-11-24 01:00 ` Rui DeSousa <rui@crazybean.net>
2018-11-24 01:19 ` Re: Logical wal receiver (background worker) not detecting when publisher node has died Rui DeSousa <rui@crazybean.net>
0 siblings, 1 reply; 3+ messages in thread
From: Rui DeSousa @ 2018-11-24 01:00 UTC (permalink / raw)
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>; +Cc: pgsql-admin@lists.postgresql.org
> On Nov 23, 2018, at 12:20 AM, Achilleas Mantzios <achill@matrix.gatewaynet.com> wrote:
>
> Dear List,
> Coming back from : https://www.postgresql.org/message-id/ae8812c3-d138-73b7-537a-a273e15ef6e1%40matrix.gatewaynet.com
>
> and having got absolutely no helpful answer from our infrastructure people, I would like to ask :
>
> Is it on earth possible that the primary (publisher node) has crushed while on the subscriber node the logical wal receiver goes on happily like there is no problem at all, no messages in log, no timeouts, acts if nothing happen ?
>
> (in the meantime the second standby instantly detected the crush of the primary and immediately restarted re-connection attempts)
>
Not that I can think of without it being a bug.
If it happens again; you can try killing the WAL receiver session via Postgres and if that fails then using tcpkill to terminate the session.
It would be good to know the actual cause though and collect as much information before terminating the session.
Interested; but not sure if it’s related: https://www.evanjones.ca/tcp-stuck-connection-mystery.html
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Logical wal receiver (background worker) not detecting when publisher node has died
2018-11-23 05:20 Logical wal receiver (background worker) not detecting when publisher node has died Achilleas Mantzios <achill@matrix.gatewaynet.com>
2018-11-24 01:00 ` Re: Logical wal receiver (background worker) not detecting when publisher node has died Rui DeSousa <rui@crazybean.net>
@ 2018-11-24 01:19 ` Rui DeSousa <rui@crazybean.net>
0 siblings, 0 replies; 3+ messages in thread
From: Rui DeSousa @ 2018-11-24 01:19 UTC (permalink / raw)
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>; +Cc: pgsql-admin@lists.postgresql.org
> On Nov 23, 2018, at 8:00 PM, Rui DeSousa <rui@crazybean.net> wrote:
>
>
>
>> On Nov 23, 2018, at 12:20 AM, Achilleas Mantzios <achill@matrix.gatewaynet.com> wrote:
>>
>> Dear List,
>> Coming back from : https://www.postgresql.org/message-id/ae8812c3-d138-73b7-537a-a273e15ef6e1%40matrix.gatewaynet.com
>>
>> and having got absolutely no helpful answer from our infrastructure people, I would like to ask :
>>
>> Is it on earth possible that the primary (publisher node) has crushed while on the subscriber node the logical wal receiver goes on happily like there is no problem at all, no messages in log, no timeouts, acts if nothing happen ?
>>
>> (in the meantime the second standby instantly detected the crush of the primary and immediately restarted re-connection attempts)
>>
>
> Not that I can think of without it being a bug.
>
> If it happens again; you can try killing the WAL receiver session via Postgres and if that fails then using tcpkill to terminate the session.
>
> It would be good to know the actual cause though and collect as much information before terminating the session.
>
> Interested; but not sure if it’s related: https://www.evanjones.ca/tcp-stuck-connection-mystery.html
>
>
>
Same problem but no solution; keep alive not working.
https://superuser.com/questions/1021988/connection-remains-flagged-as-established-even-if-host-is-un...
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2018-11-24 01:19 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-11-23 05:20 Logical wal receiver (background worker) not detecting when publisher node has died Achilleas Mantzios <achill@matrix.gatewaynet.com>
2018-11-24 01:00 ` Rui DeSousa <rui@crazybean.net>
2018-11-24 01:19 ` Rui DeSousa <rui@crazybean.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox