On Tue, Dec 1, 2009 at 5:46 PM, Kukkala Prasad <[email protected]> wrote:
> Hi All,
>
> I have configured ha cluster with two nodes and two resources IP address and 
> httpd service. I am working with heartbeat-2.1.3-3.el5.centos CentOS 5.3.

Far too old.

> I followed the 
> http://www.novell.com/documentation/sles10/heartbeat/?page=/documentation/sles10/heartbeat/data/heartbeat.html
>  documentation.
>
> I want to discuss about 2 issues and 2 questions
>
> Issue1:
> I want to stop resources on a node if the network connection is not available 
> (default gateway is not reachable).
> When I stop network of node 1 (using "service network stop" command) 
> resources are automatically launching on node2 but on node1 resources are 
> still running. Please check the below configuration and kindly advice me what 
> is missing? Sorry for the big xml but I have to share full configuration to 
> check the missing stuff.

http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ch09s03s03.html

> Issue2:
> Once the network is up resources running on node2 are moving to node1. In my 
> ha.cf file I have set auto_fallback false. But still resources are coming 
> back to node1. I don't want this. How to avoid this?

Look up resource-stickiness.

>
> Question1
> I want to implement a logic (quorum I suppose) which should enable me decide 
> whether to run resources on given node or not. This is required for me to 
> avoid accessing SAN simultaneously by two nodes. How to do this?

quorum and fencing are already supported.
the problem with quorum in 2-node heartbeat clusters is that it always
pretends that it has it.

>
> Question2
> Is there any reference configuration (cib.xml) available for 
> HeartBeat+SAN+MySQL active-passive configuration.

You could try reading the cluster form scratch document at
http://clusterlabs.org/wiki/Documentation and substitute mysql for
apache.
_______________________________________________
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