On Wed, Mar 3, 2010 at 8:21 AM, Haussecker, Armin <[email protected]> wrote: > Hi, > > we have an openais cluster consisting of two nodes, a resource is started on > first node, and this resource should remain on first node by suitable > location constraint, and also it should be started on the same node as > another resource by colocation constraint. > > If the resource is stopped, and afterwards started again, we can see that > first it is started on second node, and afterwards stopped on second node > and restarted on first node again. So, finally everything seems to work > correctly. > > But, how can we avoid that the resource is started on second node and > afterwards stopped on second node and started on first node ?? If the > resource is stopped on first node, and afterwards started again, it should > be immediately restarted on first node and not started and stopped on second > node in the meantime.
It depends on a number of things, the most important of which is the monitor function of your resource. If it returns 7 (ie. safely stopped), then the cluster has no reason to put it back on the first node. Also related is resource-stickiness _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
