Good to know it is now not needed. You are correct about logic, yes, I just
forgot details. I just recall that sbd added too much load during cluster
start and recoveries.
Thank you!
On August 23, 2020 1:23:37 PM Klaus Wenninger wrote:
On 8/21/20 8:55 PM, Vladislav Bogdanov wrote:
Hi,
On 8/21/20 8:55 PM, Vladislav Bogdanov wrote:
> Hi,
>
> btw, is sbd is now able to handle cib diffs internally?
> Last time I tried to use it with frequently changing CIB, it became a
> CPU hog - it requested full CIB copy on every change.
Actually sbd should have been able to handle cib-diffs
On 8/22/20 11:02 AM, Andrei Borzenkov wrote:
> 21.08.2020 21:16, Ken Gaillot пишет:
>> Previously at shutdown, sbd determined a clean pacemaker shutdown by
>> checking whether any resources were running at shutdown. This would
>> lead to sbd fencing if pacemaker shut down in maintenance mode with
21.08.2020 21:16, Ken Gaillot пишет:
>
> Previously at shutdown, sbd determined a clean pacemaker shutdown by
> checking whether any resources were running at shutdown. This would
> lead to sbd fencing if pacemaker shut down in maintenance mode with
> resources active.
What conditions lead to
Hi,
btw, is sbd is now able to handle cib diffs internally?
Last time I tried to use it with frequently changing CIB, it became a
CPU hog - it requested full CIB copy on every change.
Fri, 21/08/2020 в 13:16 -0500, Ken Gaillot wrote:
> Hi all,
>
> Looking ahead to the Pacemaker 2.0.5 release
Hi all,
Looking ahead to the Pacemaker 2.0.5 release expected toward the end of
this year, we will have improvements of interest to anyone running
clusters with sbd.
Previously at start-up, if sbd was blocked from contacting Pacemaker's
CIB in a way that looked like pacemaker wasn't running
