On Mon, Nov 15, 2021 at 3:32 PM S Rogers <sa.rogers1...@gmail.com> wrote: >> >> The only solution here - as long as fencing node on external >> connectivity loss is acceptable - is modifying ethmonitor RA to fail >> monitor operation in this case. > > I was hoping to find a way to achieve the desired outcome without resorting > to a custom RA, but it does appear to be the only solution. >
Well, looking at it from a different angle - you could use the knet nozzle interface for replication which means your postgres connectivity is guaranteed to be the same as pacemaker/corosync connectivity. _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
