Re: [ClusterLabs] Using "mandatory" startup order but avoiding depending clones from restart after member of parent clone fails

On 02/06/2017 05:25 PM, Alejandro Comisario wrote: > guys, really happy to post my first doubt. > > i'm kinda having an "conceptual" issue that's bringing me, lots of issues > i need to ensure that order of starting resources are mandatory but > that is causing me a huge issue, that is if just

Re: [ClusterLabs] Antw: Re: Antw: Re: Pacemaker kill does not cause node fault ???

Ken Gaillot writes: > On 02/07/2017 01:11 AM, Ulrich Windl wrote: > >> Ken Gaillot writes: >> >>> On 02/06/2017 03:28 AM, Ulrich Windl wrote: >>> Isn't the question: Is crmd a process that is expected to die (and thus need restarting)? Or

Re: [ClusterLabs] Pacemaker kill does not cause node fault ???

Ken Gaillot writes: > On 02/03/2017 07:00 AM, RaSca wrote: >> >> On 03/02/2017 11:06, Ferenc Wágner wrote: >>> Ken Gaillot writes: >>> On 01/10/2017 04:24 AM, Stefan Schloesser wrote: > I am currently testing a 2 node cluster under Ubuntu

[ClusterLabs] Failed reload

Hi, There was an interesting discussion on this list about "Doing reload right" last July (which I still haven't digested entirely). Now I've got a related question about the current and intented behavior: what happens if a reload operation fails? I found some suggestions in