Hello,
I generated cib file with haresources2cib.py from haresources.
Then, I made sure what happens if I shutdown mysqld on primary server.
Heartbeat2 seems to restart mysqld on the same server, and if it is not sucess,
it fail-over to the secondary node.
I shutdown mysqld with "mysqladmin shutdown" command.
The question is;
"How Heartbeat2 monitor MySQL Server alive or death?"
Does it monitor mysqld process itself?
Or, does it issue some command like "mysqladmin ping" to check mysqld
availability?
Would someone point me out which page I should refer more information?
Thanks,
-----haresources-----
h1 172.20.95.50 drbddisk Filesystem::/dev/drbd0::/mnt/drbd::ext3 mysql
-----cib.xml-----
<?xml version="1.0" ?>
<cib admin_epoch="0" epoch="0" num_updates="0">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
<nvpair
id="cib-bootstrap-options-symmetric-cluster"
name="symmetric-cluster" value="true"/>
<nvpair
id="cib-bootstrap-options-no_quorum-policy"
name="no_quorum-policy" value="stop"/>
<nvpair
id="cib-bootstrap-options-default-resource-stickiness"
name="default-resource-stickiness" value="0"/>
<nvpair
id="cib-bootstrap-options-default-resource-failure-stickiness"
name="default-resource-failure-stickiness" value="0"/>
<nvpair
id="cib-bootstrap-options-stonith-enabled"
name="stonith-enabled" value="false"/>
<nvpair
id="cib-bootstrap-options-stonith-action"
name="stonith-action" value="reboot"/>
<nvpair
id="cib-bootstrap-options-stop-orphan-resources"
name="stop-orphan-resources" value="true"/>
<nvpair
id="cib-bootstrap-options-stop-orphan-actions"
name="stop-orphan-actions" value="true"/>
<nvpair
id="cib-bootstrap-options-remove-after-stop"
name="remove-after-stop" value="false"/>
<nvpair
id="cib-bootstrap-options-short-resource-names"
name="short-resource-names" value="true"/>
<nvpair
id="cib-bootstrap-options-transition-idle-timeout"
name="transition-idle-timeout" value="5min"/>
<nvpair
id="cib-bootstrap-options-default-action-timeout"
name="default-action-timeout" value="5s"/>
<nvpair
id="cib-bootstrap-options-is-managed-default"
name="is-managed-default" value="true"/>
</attributes>
</cluster_property_set>
</crm_config>
<nodes/>
<resources>
<group id="group_1">
<primitive class="ocf" id="IPaddr_172_20_95_50"
provider="heartbeat" type="IPaddr">
<operations>
<op
id="IPaddr_172_20_95_50_mon" interval="5s" name="monitor"
timeout="5s"/>
</operations>
<instance_attributes
id="IPaddr_172_20_95_50_inst_attr">
<attributes>
<nvpair
id="IPaddr_172_20_95_50_attr_0" name="ip" value="172.20.95.50"/>
</attributes>
</instance_attributes>
</primitive>
<primitive class="heartbeat" id="drbddisk_2"
provider="heartbeat"
type="drbddisk">
<operations>
<op id="drbddisk_2_mon"
interval="120s" name="monitor" timeout="60s"/>
</operations>
</primitive>
<primitive class="ocf" id="Filesystem_3"
provider="heartbeat"
type="Filesystem">
<operations>
<op id="Filesystem_3_mon"
interval="120s" name="monitor" timeout="60s"/>
</operations>
<instance_attributes
id="Filesystem_3_inst_attr">
<attributes>
<nvpair
id="Filesystem_3_attr_0" name="device" value="/dev/drbd0"/>
<nvpair
id="Filesystem_3_attr_1" name="directory" value="/mnt/drbd"/>
<nvpair
id="Filesystem_3_attr_2" name="fstype" value="ext3"/>
</attributes>
</instance_attributes>
</primitive>
<primitive class="heartbeat" id="mysql_4"
provider="heartbeat" type="mysql">
<operations>
<op id="mysql_4_mon"
interval="120s" name="monitor" timeout="60s"/>
</operations>
</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="h1"/>
</rule>
</rsc_location>
</constraints>
</configuration>
<status/>
</cib>
-----
--
[EMAIL PROTECTED]
Kenji Hirohama
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
