Re: [ClusterLabs] pacemaker with sbd fails to start if node reboots too fast.

30.11.2017 13:48, Gao,Yan пишет: > On 11/22/2017 08:01 PM, Andrei Borzenkov wrote: >> SLES12 SP2 with pacemaker 1.1.15-21.1-e174ec8; two node cluster with >> VM on VSphere using shared VMDK as SBD. During basic tests by killing >> corosync and forcing STONITH pacemaker was not started after reboot.

Re: [ClusterLabs] Should pacemaker pursue its own and corosync's instant resurrection if either dies? (Was: Is corosync supposed to be restarted if it dies?)

02.12.2017 16:30, Jan Pokorný пишет: > > In race-condition free situation, such a BindsTo-incurred stopping (or > at least scheduled to since 235?) of the service is then not a subject > of auto-restarting, from what I've observed, and documentation agrees: > > Restart= [...] When the death of

Re: [ClusterLabs] systemd's TasksMax and pacemaker

On 15/11/17 11:16 +0100, Jan Pokorný wrote: > On 14/11/17 15:07 -0600, Ken Gaillot wrote: >> It is conceivable in a large cluster that Pacemaker could exceed >> this limit > > [of 512 or 4915 tasks allowed per service process tree, possibly > overridden with systemd-system.conf(5) configuration],

[ClusterLabs] Should pacemaker pursue its own and corosync's instant resurrection if either dies? (Was: Is corosync supposed to be restarted if it dies?)

On 30/11/17 11:00 +0300, Andrei Borzenkov wrote: > On Thu, Nov 30, 2017 at 12:42 AM, Jan Pokorný wrote: >> On 29/11/17 22:00 +0100, Jan Pokorný wrote: >>> On 28/11/17 22:35 +0300, Andrei Borzenkov wrote: I'm not sure what is expected outcome, but pacemaker.service is still restarted (due