Re: [ClusterLabs] clearing failed actions

On 06/19/2017 04:54 PM, Attila Megyeri wrote: > One more thing to add. > Two almost identical clusters, with the identical asterisk primitive produce > a different crm_verify output. on one cluster, it returns no warnings, > whereas the other once complains: > > On the problematic one: > >

[ClusterLabs] ocf_take_lock is NOT actually safe to use

Repost to a wider audience, to raise awareness for this. ocf_take_lock may or may not be better than nothing. It at least "annotates" that the auther would like to protect something that is considered a "critical region" of the resource agent. At the same time, it does NOT deliver what the name

Re: [ClusterLabs] Pacemaker 1.1.17 Release Candidate 4 (likely final)

On 06/21/2017 02:58 AM, Ferenc Wágner wrote: > Ken Gaillot writes: > >> The most significant change in this release is a new cluster option to >> improve scalability. >> >> As users start to create clusters with hundreds of resources and many >> nodes, one bottleneck is a

Re: [ClusterLabs] Pacemaker 1.1.17 Release Candidate 4 (likely final)

Ken Gaillot writes: > The most significant change in this release is a new cluster option to > improve scalability. > > As users start to create clusters with hundreds of resources and many > nodes, one bottleneck is a complete reprobe of all resources (for > example, after