I have set up a new 2 node environment that right now only runs httpd.
I use heartbeat 2.0.8.
If I stop the heartbeat on master then slave takes over, and if I power off
master then slave takes over, but if I kill the httpd service on master then
nothing happens.
I have been digging through as much documentation as I can but can't really
find how to make this an 'all or none' scenario. I will be adding more services
to this mixture and want a full fail-over to slave or back to master if
ANYTHING fails to check out OK.
cib.xml (generated by haresources2cib.py) :
<cib admin_epoch="0" have_quorum="true" ignore_dtd="false" num_peers="2"
cib_feature_revision="1.3" ccm_transition="2" generated="true"
dc_uuid="84cb8944-c4a6-4b50-9059-a43bfc17b695" epoch="3" num_updates="61"
cib-last-written="Thu Jul 23 12:26:50 2009">
<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>
<node id="9576ed55-a5fe-4e5b-b1ef-f9935e3b9917" uname="master"
type="normal"/>
<node id="84cb8944-c4a6-4b50-9059-a43bfc17b695" uname="slave"
type="normal"/>
</nodes>
<resources>
<group id="group_1">
<primitive class="ocf" id="IPaddr_192_168_56_107" provider="heartbeat"
type="IPaddr">
<operations>
<op id="IPaddr_192_168_56_107_mon" interval="5s" name="monitor"
timeout="5s"/>
</operations>
<instance_attributes id="IPaddr_192_168_56_107_inst_attr">
<attributes>
<nvpair id="IPaddr_192_168_56_107_attr_0" name="ip"
value="192.168.56.107"/>
</attributes>
</instance_attributes>
</primitive>
<primitive class="lsb" id="httpd_2" provider="heartbeat" type="httpd">
<operations>
<op id="httpd_2_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="master"/>
</rule>
</rsc_location>
</constraints>
</configuration>
</cib>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
