From: Rui DeSousa <rui@crazybean.net>
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Logical wal receiver (background worker) not detecting when publisher node has died
Date: Fri, 23 Nov 2018 20:00:13 -0500
Message-ID: <849F7F83-090C-41F8-91B6-FF20E736B060@crazybean.net> (raw)
In-Reply-To: <cd6ba6d5-d76d-4a69-a743-00544ec2dbca@matrix.gatewaynet.com>
References: <cd6ba6d5-d76d-4a69-a743-00544ec2dbca@matrix.gatewaynet.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: rui@crazybean.net, achill@matrix.gatewaynet.com
Subject: Re: Logical wal receiver (background worker) not detecting when publisher node has died
In-Reply-To: <849F7F83-090C-41F8-91B6-FF20E736B060@crazybean.net>
References: <cd6ba6d5-d76d-4a69-a743-00544ec2dbca@matrix.gatewaynet.com> <849F7F83-090C-41F8-91B6-FF20E736B060@crazybean.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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