Yes,
I did it on RHEL5, it was a setting, backline me tomorrow and I will try
and find that config.
Basically if the HA fails over, from node1 to node2. You want it to stay
on node2 until you interviene.
This prevents a contention issue where both servers are primary node.
Rois Cannon wrote:
Michael / all,
Any chance you figured out how to keep ha from going back to node1
without human intervention?
Rois
This is my dilemma:
I'm building a simple 2 node cluster, node1 and node2.
HA works fine so far.
If I issue "network stop" on node1, HA jumps in and transfers resources to
node2.
Good so far.
However, when I issue "network start" on node1 HA grabs all the resources
back and wants to be preferred node again.
I want node1 to NEVER return to the cluster without manual intervention.
Is this possible?
>From the name of the STONITH suicide device it sounded like it would allow
node1 to simply kill itself and avoid returning to the cluster.
I am using 2 bcast interfaces (serial is out of the question) and IPFAIL.
Any Help?
Thanks
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
