Also,there is a way to tell the cluster to cleanup failures -> failure-timeoutÂ
Best Regards,Strahil Nikolov
On Sat, Feb 19, 2022 at 1:52, Jehan-Guillaume de Rorthais
wrote: Hello,
On Fri, 18 Feb 2022 21:44:58 +
"Larry G. Mills" wrote:
> ... This happened again recently, and the
Hello,
On Fri, 18 Feb 2022 21:44:58 +
"Larry G. Mills" wrote:
> ... This happened again recently, and the running primary DB was demoted and
> then re-promoted to be the running primary. What I'm having trouble
> understanding is why the running Master/primary DB was demoted. After the
>
Hello all,
I have a two-node Pacemaker cluster configured with a high-availability
PostgreSQL resource. Occasionally, I notice that when the Master/primary DB
is running under significant write load, the cluster "monitor" operation will
time out, thus incrementing the failcount for the ha-db
