Hi,
I just want to let you know that the problem is solved. Thanks to "crm_mon
-f". ;)
The error was the usage of the pingd RA. This RA worked very unreliable and
is marked as deprecated though (
http://comments.gmane.org/gmane.linux.highavailability.user/32290).
So after changing the RA to ocf:pa
Hi Mike,
thank you for the advice.
Referring to my actual knowledge the resource stickiness just defines that a
resource should remain to the node it is running on.
The failover and failback actions are performed correctly with the location
contraints that bind the resources to a specific node wh
Simon,
I'm new to this, so if this doesn't help, don't despair - the more
experienced members will be along shortly. :-)
Could it be that you need "stickyness?"
I think that's the term for the concept you are describing.
Also, if that's a two node cluster, have you defined cluster property
no-q
With the help of "crm_mon -f" I found out that just one node has the right
pingd score.
Migration summary:
* Node node1: pingd=3
* Node node2: pingd=0
When I intiate a failover by setting node1 to standby the pingd score on
node2 becomes 3.
A ping that is run manually arrives the destina
Hi,
I'm trying to set up location contraints for my cluster, but I don't get
them to work in the way that I want.
The constraints should implement the following behaviour:
- Normal operation
msDRBD0 and resIP0 start on node1, msDRBD1 and resIP1 start on node2
- Loss of network connection
When the
