On Dec 11, 2007, at 12:00 PM, Franck Ganachaud wrote:
Thanks Andrew
I change the configuration to this :
<resources>
<clone id="MySQL_ORB" interleave="false" is_managed="true"
notify="false" ordered="false">
<instance_attributes id="MySQL_ORB_inst_attr">
<attributes>
<nvpair id="MySQL_ORB_attr_0" name="clone_max" value="2"/>
<nvpair id="MySQL_ORB_attr_1" name="clone_node_max"
value="1"/>
</attributes>
</instance_attributes>
<primitive class="ocf" id="mysql_orb1" is_managed="false"
provider="heartbeat" type="mysql_orb">
<operations>
<op id="mysql_orb_mon" interval="30s" name="monitor"
on_fail="stop" timeout="30s"/>
</operations>
</primitive>
</clone>
<group id="group_1" restart_type="restart">
<primitive class="ocf" id="IPaddr_Cluster"
provider="heartbeat" type="IPaddr">
<operations>
<op id="IPaddr_Cluster_mon" interval="5s" name="monitor"
timeout="5s"/>
</operations>
<instance_attributes id="IPaddr_Cluster_inst_attr">
<attributes>
<nvpair id="IPaddr_Cluster_attr_0" name="ip"
value="192.168.87.100"/>
</attributes>
</instance_attributes>
</primitive>
<primitive class="ocf" id="apache_2" provider="heartbeat"
type="apache">
<operations>
<op id="apache_2_mon" interval="30s" name="monitor"
timeout="30s"/>
</operations>
<instance_attributes id="apache_2_inst_attr">
<attributes>
<nvpair id="apache_2_attr_0" name="configfile" value="/
usr/local/apache/conf/httpd.conf"/>
</attributes>
</instance_attributes>
</primitive>
</group>
</resources>
<constraints>
<rsc_location id="rsc_location_group_1" rsc="group_1">
<rule id="prefered_location_group_1" score="100">
<expression attribute="#uname"
id="prefered_location_group_1_expr" operation="eq" value="server_a"/>
</rule>
</rsc_location>
<rsc_colocation from="group_1" id="web_if_mysql"
score="INFINITY" to="MySQL_ORB"/>
</constraints>
With this configuration, DB monitoring doesn't occur anymore. For
the is_managed parameter, I don't know what to set between the clone
and primitive inside the clone to have the good behaviour : don't
start/stop it at startup, just monitor.
hmmm... i forgot we don't start recurring monitor actions for
unmanaged resources.
if the monitor was already running, then we wouldn't stop it if you
change the resource to unmanaged... but that doesn't help you :-(
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
