[pgpool-general: 7816] broken pipe in the logs

[Aditya Patawari]

Hello.

We are running a small self-managed pgpool and postgres setup in Google
cloud. We have setup two Pgpools which connect to one primary and two
replica postgres setup.

On more than one occasion, one of the pgpools has printed a "Broken pipe"
error and the backend went unreachable for that pgpool, while the other
pgpool was able to reach the backend postgres just fine. The bad pgpool
will only start working after a restart of the pgpool.

I would really appreciate some help in understanding why this is happening
and what can be done to mitigate this issue.

Log lines, are added below:

Oct 19 13:05:31 pgpool-fdfv pgpool[935]: 2021-07-21 13:05:31: pid
10003: LOG:  received degenerate backend request for node_id: 1 from
pid [10003]
Oct 19 13:05:31 pgpool-fdfv pgpool[935]: 2021-07-21 13:05:31: pid 935:
LOG:  Pgpool-II parent process has received failover request
Oct 19 13:05:31 pgpool-fdfv pgpool[935]: 2021-07-21 13:05:31: pid
10003: WARNING:  write on backend 1 failed with error :"Broken pipe"
Oct 19 13:05:31 pgpool-fdfv pgpool[935]: 2021-07-21 13:05:31: pid
10003: DETAIL:  while trying to write data from offset: 0 wlen: 5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20211020/978fa23b/attachment.htm>