Re: [ClusterLabs] Make sure either 0 or all resources in a group are running

Unstandby-ing a node automatically at some point after a failure on certain resources actually fits our use cases well, but the problem is that the automatic unstandby does not put DRBD into secondary mode once it occurs. A manual pcs cluster standby $(uname -n) and pcs cluster unstandby $(uname

Re: [ClusterLabs] Make sure either 0 or all resources in a group are running

'on-fail=standby' works well, however, setting a failure-timeout appears to automatically bring the node out of standby after it expires. -- Sam Gardner Trustwave | SMART SECURITY ON DEMAND On 3/28/16, 3:31 PM, "Ken Gaillot" wrote: >On 03/28/2016 02:19 PM, Sam

Re: [ClusterLabs] Resource failure-timeout does not reset when resource fails to connect to both nodes

On 28/03/16 12:44 PM, Sam Gardner wrote: > I have a simple resource defined: > > [root@ha-d1 ~]# pcs resource show dmz1 > Resource: dmz1 (class=ocf provider=internal type=ip-address) > Attributes: address=172.16.10.192 monitor_link=true > Meta Attrs: migration-threshold=3 failure-timeout=30s

[ClusterLabs] Resource failure-timeout does not reset when resource fails to connect to both nodes

I have a simple resource defined: [root@ha-d1 ~]# pcs resource show dmz1 Resource: dmz1 (class=ocf provider=internal type=ip-address) Attributes: address=172.16.10.192 monitor_link=true Meta Attrs: migration-threshold=3 failure-timeout=30s Operations: monitor interval=7s