hi all,
when I test the heartbeat-2.1.4, I find that resource of a node will
migrate to other node when other node's status change. Fox example, the
configuration of my cluster is as follows:
4 nodes: A, B, C and D;
2 resource groups: rs_1, rs_2;
every resource groups contain one vip and one service ;
the original status of the cluster as follows:
node A: on line,
node B: on line,
node C: on line (resource group rs_2 run on node C),
node D: on line (resource group rs_1 run on node D),
When I stop the heartbeat on node C (using command: /etc/rc.d/heartbeat stop),
the status of the cluster changed as follows:
node A: on line,
node B: on line (resource group rs_1 run on node B),
node C: off line
node D: on line (resource group rs_2 run on node D),
We found that resource group rs_2(on node D before) migrate to node B, only
because node C's status changed from online to offline, but node D 's status
haven't changed. How can I avoid it.
I hope that resource group can stand on the same node, if the node's status is
not changed.
Thanks in advance!_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
