[pgpool-general: 6669] Re: active/active with Consul service

Matthew Tice mjtice at gmail.com
Fri Aug 9 22:07:08 JST 2019

I guess mainly I'm concerned that by having this "active/active"
configuration I may cause some problems.  Looking at the documentation this
paragraph notes:

When a backend node status changes by failover etc.., watchdog notifies the
> information to other Pgpool-II nodes and synchronizes them. When online
> recovery occurs, watchdog restricts client connections to other Pgpool-II nodes
> for avoiding inconsistency between backends.

What is the "inconsistency", specifically?  I'm not opposed to using
watchdog per se, I just don't want to have to manage a vip when I can use
the functionality included in my consul cluster.

On Thu, Aug 8, 2019 at 2:51 PM Pierre Timmermans <ptim007 at yahoo.com> wrote:

> I believe this will work but i don't see a real plus value for pgpool in
> this set-up
> Note that the watchdog mode of pgpool works with two nodes, simply you
> should  protect against a network partition (for this you need a third
> server that can act as a trusted server, you just need an IP address not
> the server)
> P.
> Sent from Yahoo Mail on Android
> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
> On Thu, 8 Aug 2019 at 22:36, Matthew Tice
> <mjtice at gmail.com> wrote:
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190809/c84da313/attachment.html>

More information about the pgpool-general mailing list