Re: [ClusterLabs] Set a node attribute for multiple nodes with one command

2016-11-18 Thread Ken Gaillot
On 11/18/2016 08:55 AM, Kostiantyn Ponomarenko wrote: > Hi folks, > > Is there a way to set a node attribute to the "status" section for few > nodes at the same time? > > In my case there is a node attribute which allows some resources to > start in the cluster if it is set. > If I set this node

[ClusterLabs] Set a node attribute for multiple nodes with one command

2016-11-18 Thread Kostiantyn Ponomarenko
Hi folks, Is there a way to set a node attribute to the "status" section for few nodes at the same time? In my case there is a node attribute which allows some resources to start in the cluster if it is set. If I set this node attribute for say two nodes in a way - one and then another, than

[ClusterLabs] Antw: Re: ocf:heartbeat:apache does not start

2016-11-18 Thread Ulrich Windl
Hi! As an exercise you could try to write your own apache RA. That shouldn't bee to difficult. Alternatively you could try to hack the RA until it works. Then report your insights. Maybe you want to stop your apache and try "ocf-tester (if available) to test the RA (also good when hacking it).

Re: [ClusterLabs] Query about resource stickiness

2016-11-18 Thread Kostiantyn Ponomarenko
Phanidhar, If you don't have any location rules in your cluster, you can try setting "resource-stickiness=1" or "resource-stickiness=100". That will do the same job as INFINITY if there is no other location rules in the cluster. Also, there is a way to see current state of scores in the cluster,

Re: [ClusterLabs] Query about resource stickiness

2016-11-18 Thread phanidhar prattipati
Thanks for the prompt reply Ken. In my configuration none of my resource have any node priorities set but in 3 node when one nodes goes down and is added back to the cluster some times resources are getting struck between newly added node and on other node where it is presently running after