[Linux-HA] stickiness for master in master/slave resource?

[Stefan Lasiewski]

Have you had any further success with this problem?

> Then the second nodes gets promoted again
> and the drbd starts up again on the second node.

I believe I ran into the same problem as you. I am trying to fail
IPaddr, nfs and nfslock. I don't think this is related to your use of
DRBD.

As I understand the documentation, "resource_stickiness=INFINITY"
means that the resources should 'stick' to it's current node until it
is forced to another node.
(http://www.linux-ha.org/v2/dtd1.0/annotated#default_resource_stickiness
)

However, this doesn't always happen. In my case:

1. Failover from primary host to standby host works fine, and the
resources properly move from primary to standby.
2. Primary starts back up. The resources remain on the standby host.
This is expected, because the 'resource_stickiness=INFINITY'.
3. I can manually migrate services the standby host to the primary host fine.
4. At this point, I should be done.

However, at this point I run into a serious problem. If I reboot the
standby node, resources will then migrate over to the standby node.
This seems very wrong.

-- 
Stefan Lasiewski
http://stefanco.com