[pgpool-general: 6456] Re: trusted_servers
amazinglifetime at gmail.com
Fri Mar 15 01:36:03 JST 2019
Can anyone from the development team confirm? I didn't find much
documentation for this parameter too, is there any?
On Thu, Mar 14, 2019 at 3:29 AM Pierre Timmermans <ptim007 at yahoo.com> wrote:
> My understanding is that pgpool watchdog will shut off a node when the
> trusted server cannot be reached, i.e. I don't believe the test is done
> only after degenerated state was detected. I am not 100% sure, I'll have to
> test again.
> So the problem is that this trusted server is now the single point of
> failure ! But you can put a list of IP addresses in this config, so I would
> also add the ip addresses of the other watchdog node: this way watchdog
> will not kill a node as long as it can see the other one.
> On Wednesday, March 13, 2019, 2:28:30 PM GMT+1, Alexander Dorogensky <
> amazinglifetime at gmail.com> wrote:
> Hi everyone,
> We generally set this parameter to one host to remedy split brain
> situations but some customers have unreliable networks and therefore ping
> to that host would fail and pgpool would shut down.
> My understanding was that trusted server(s) connection will only be tested
> after degenerated state was detected (before triggering failover), is it
> If not.. how do I configure trusted servers in a flaky network?
> pgpool-general mailing list
> pgpool-general at pgpool.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pgpool-general