[pgpool-general: 7507] Re: pgpool2 in kubernetes dies

[Nathan Ward]

> On 14/04/2021, at 2:21 AM, Nikolay Mastilo (HM) <nikm71 at hotmail.com> wrote:
> 
> Hello. The approach with tuning tcp timeouts is workable but in some circumstance it is not applicable. Our customer needs solution with configuration only in software components, such as: pgpool, postgresql, etc. The networks where such solution will be deployed can be unpredictably different in different network components. So, our solution should be configurable itself for different network environments.
> 
I think you will have a hard time with requirements like that, and asking for free support.
> We found out that in the event of shortterm loss of connection between pgpool and database, pgpool  detaches node from the pool and doesn't reconnect its own without restarting. Besides it, clients that were connected to pgpool have disconnected and cannot reconnect until pgpool is restarted. 
> 
> The point is that in our solution we use pgpool as connection pooler and load balancer only, without controling cluster. Failoving management is carried out by patroni. 
> 
> Could anyone advise any pgpool parameters set configuration when pgpool never detach nodes from its pool but try reconnect with specified period and continue interact with the client.
> 
I think you’re looking for auto_failback.

--
Nathan Ward


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20210414/4dcfafb3/attachment.htm>