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 run
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
> mo
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
On Fri, 2022-02-18 at 16:00 +0100, Lentes, Bernd wrote:
>
> - On Feb 17, 2022, at 4:25 PM, kgaillot kgail...@redhat.com
> wrote:
> > > So for me the big question is:
> > > When a transition is happening, and there is a change in the
> > > cluster,
> > > is the transition "aborted"
> > > (delay
- On Feb 17, 2022, at 4:25 PM, kgaillot kgail...@redhat.com wrote:
>> So for me the big question is:
>> When a transition is happening, and there is a change in the cluster,
>> is the transition "aborted"
>> (delayed or interrupted would be better) or not ?
>> Is this behaviour consistent ? I
