[Pacemaker] Ordering set of resources, problem in ordering chain of resources

[rakesh k]

Hi All

I had configured Heartbeeat, pacemkaer on my two VM's

Cluster with two nodes, two nodes are running *cent-os* as operation
systems.

Cluster configured with 8 resources and defined order, taking reference
pacemaker explained

please find the order and co-location constraints, taken from cib.xml

<rsc_colocation id="Httpd-with-ip" rsc="HttpdVIP" score="INFINITY"
with-rsc="Httpd"/>
<rsc_colocation id="Tomcat1-with-ip" rsc="Tomcat1VIP" score="INFINITY"
with-rsc="Tomcat1"/>
<rsc_colocation id="Mysql-with-ip" rsc="MysqlVIP" score="INFINITY"
with-rsc="MS_Mysql" with-rsc-role="Master"/>
<rsc_order first="HttpdVIP" id="Httpd-after-op" score="INFINITY"
then="Httpd"/>
<rsc_order first="MysqlVIP" id="Mysql-after-ip" score="INFINITY"
then="MS_Mysql"/>
<rsc_order first="Tomcat1VIP" id="Tomcat1-after-ip" score="INFINITY"
then="Tomcat1"/>
<rsc_order first="MS_Mysql" id="Tomcat1-after-MYSQL" score="INFINITY"
then="Tomcat1VIP"/>
<rsc_colocation id="Tomcat2-with-Tomcat" rsc="Tomcat1" score="INFINITY"
with-rsc="Tomcat2VIP"/>
<rsc_order first="Tomcat2VIP" id="Tomcat2-after-ip" score="INFINITY"
then="Tomcat2"/>
<rsc_order first="Tomcat2" id="Httpd-after-Tomcat2" score="INFINITY"
then="Httpd"/>
<rsc_colocation id="tomcat2-with-ip" rsc="Tomcat2VIP" score="INFINITY"
with-rsc="Tomcat2"/>

so when heartbeat start on both nodes, the order resources started are
MysqlVIP-->MSMysql-->tomcat1VIP-->Tomcat-->Tomcat2VIP-->tomcat2-->HttpdVIP-->Httpd

My question is when i try to stop Mysql process since there is an order
constraint .all the resources should stop, but still, when i do *crm_mon  *i
see tomcat2,tomcat2vip,http,httpdVIP resources running on cluster frame work
, can you please suggest me if there is any flaw in determining the order or
co-location constraints.



Regards
Rakesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110419/cbc19101/attachment-0003.html>