Re: [ClusterLabs] corosync race condition when node leaves immediately after joining

On 13/11/17 17:06, Jan Friesse wrote: Jonathan, I've finished (I hope) proper fix for problem you've seen, so can you please try to test https://github.com/corosync/corosync/pull/280 Thanks, Honza Hi Honza, Hi Jonathan, Thanks very much for putting this fix together. I'm happy to

Re: [ClusterLabs] Pacemaker responsible of DRBD and a systemd resource

I've driven for 22 years and never needed my seatbelt before, but yet, I still make sure I use it every time I am in a car. ;) Why it happened now is perhaps an interesting question, but it is one I would try to answer after fixing the core problem. cheers, digimer On 2017-11-15 03:37 PM, Derek

Re: [ClusterLabs] Pacemaker responsible of DRBD and a systemd resource

And just to make sure, I’m not the kind of person who stick to the “we always did it that way…” ;) Just trying to figure out why it suddenly breaks. -derek -- Derek Wuelfrath dwuelfr...@inverse.ca :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110) Inverse inc. ::

Re: [ClusterLabs] Pacemaker responsible of DRBD and a systemd resource

I agree. Thing is, we have this kind of setup deployed largely and since a while. Never ran into any issue. Not sure if something changed in Corosync/Pacemaker code or way of dealing with systemd resources. As said, without a systemd resource, everything just work as it should… 100% of the time

Re: [ClusterLabs] systemd's TasksMax and pacemaker

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], > so we are now recommending that users set TasksMax=