[Linux-HA] 4 node cluster - quorum/stonith

Joseph Smith smithj at iivip.com
Mon Oct 31 12:08:06 MST 2005


Hello list!

I am setting up a 4 node cluster. Each node in the cluster runs a webserver. 
If 1 or more go down I want the remaining to take over. I have this working 
fine, unless more than 1 go down and I lose quorum.

I understand for this to work I need to use stonith. I am a little lost on how 
I should set this up. Here is my current cib.xml:

<cib>
   <configuration>
      <crm_config>
         <nvpair id="transition_idle_timeout" name="transition_idle_timeout" 
value="120s"/>
         <nvpair id="symmetric_cluster" name="symmetric_cluster" 
value="true"/>
         <nvpair id="no_quorum_policy" name="no_quorum_policy" value="stop"/>
      </crm_config>
      <nodes/>
      <resources>
         <primitive class="ocf" id="IPaddr_1" provider="heartbeat" 
type="IPaddr">
            <operations>
               <op id="1" interval="5s" name="monitor" timeout="5s"/>
            </operations>
            <instance_attributes>
               <attributes>
                  <nvpair name="ip" value="206.157.72.249"/>
               </attributes>
            </instance_attributes>
         </primitive>
         <primitive class="ocf" id="IPaddr_2" provider="heartbeat" 
type="IPaddr">
            <operations>
               <op id="2" interval="5s" name="monitor" timeout="5s"/>
            </operations>
            <instance_attributes>
               <attributes>
                  <nvpair name="ip" value="206.157.72.147"/>
               </attributes>
            </instance_attributes>
         </primitive>
         <primitive class="ocf" id="IPaddr_3" provider="heartbeat" 
type="IPaddr">
            <operations>
               <op id="3" interval="5s" name="monitor" timeout="5s"/>
            </operations>
            <instance_attributes>
               <attributes>
                  <nvpair name="ip" value="206.157.72.139"/>
               </attributes>
            </instance_attributes>
         </primitive>
         <primitive class="ocf" id="IPaddr_4" provider="heartbeat" 
type="IPaddr">
            <operations>
               <op id="4" interval="5s" name="monitor" timeout="5s"/>
            </operations>
            <instance_attributes>
               <attributes>
                  <nvpair name="ip" value="206.157.72.195"/>
               </attributes>
            </instance_attributes>
         </primitive>
      </resources>
      <constraints>
         <rsc_location id="rsc_location_IPaddr_1" rsc="IPaddr_1">
            <rule id="prefered_location_IPaddr_1" score="INFINITY">
               <expression attribute="#uname" operation="eq" 
value="el4.interact.nonreg"/>
            </rule>
         </rsc_location>
         <rsc_location id="rsc_location_IPaddr_2" rsc="IPaddr_2">
            <rule id="prefered_location_IPaddr_2" score="INFINITY">
               <expression attribute="#uname" operation="eq" 
value="fdcore3.interact.nonreg"/>
            </rule>
         </rsc_location>
         <rsc_location id="rsc_location_IPaddr_3" rsc="IPaddr_3">
            <rule id="prefered_location_IPaddr_3" score="INFINITY">
               <expression attribute="#uname" operation="eq" 
value="hpinsa2.interact.nonreg"/>
            </rule>
         </rsc_location>
         <rsc_location id="rsc_location_IPaddr_4" rsc="IPaddr_4">
            <rule id="prefered_location_IPaddr_4" score="INFINITY">
               <expression attribute="#uname" operation="eq" 
value="modemtest.interact.nonreg"/>
            </rule>
         </rsc_location>
      </constraints>
   </configuration>
   <status/>
</cib>


Thanks,
Joe



More information about the Linux-HA mailing list