Hi,

In the past sometimes the following happened on my Heartbeat 2.1.14 cluster:

2-Node Cluster, all resources run one node - no location constraints
Now I restarted the "standby" node (which had no resources running but 
was still active inside the cluster).
When it came back online and joined the cluster again 3 different 
scenarios happened:

1. all resources failed over to the newly joined node
2. all resources stay on the current node but get restarted!
3. nothing happens

Now I don't know why 1. or 2. happen but I remember seeing a mail on the 
mailing list from someone with a similiar problem. Is there any way to 
make sure heartbeat does NOT touch the resources, especially not 
restarting or re-locating them?

Thanks in advance,
Tobi
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to