And to answer to your question:

I have created simple 2-node cluster with 4 drbd multi-state resources
and xen DomU on it with enabled stonith and setting:
default_resource_stickiness=INFINITY and
default_resource_failure_stickiness=-INFINITY.
The idea for cluster working is:
1. promote all drdd resources on node sles236 and start drbd resources
on node sles238. (works OK)
2. when failure of drbd occurs -> promote all drbd resources on
sles238 and reboot sles236.
3. when sles236 join back to the cluster after reboot, leave drbd
promoted on sles238.
I thought that setting: default_resource_stickiness=INFINITY and
default_resource_failure_stickiness=-INFINITY guarantee this bahaviour
but in fact I have:
- when sles236 join back to the cluster after reboot, all drbd
resources are demoted on sles238 and promoted on sles36. Where is
mistake in my cib.xml?

...

     <constraints>
       <rsc_location id="pref_location_drbd0" rsc="ms-drbd0">
         <rule id="sles236_location_drbd0" score="100"
boolean_op="and" role="Master">
           <expression attribute="#uname" id="drbd0_on_sles236"
operation="eq" value="sles236"/>
         </rule>
       </rsc_location>
       <rsc_location id="pref_location_drbd1" rsc="ms-drbd1">
         <rule id="sles236_location_drbd1" score="100"
boolean_op="and" role="Master">
           <expression attribute="#uname" id="drbd1_on_sles236"
operation="eq" value="sles236"/>
         </rule>
       </rsc_location>
       <rsc_location id="pref_location_drbd2" rsc="ms-drbd2">
         <rule id="sles236_location_drbd2" score="100"
boolean_op="and" role="Master">
           <expression attribute="#uname" id="drbd2_on_sles236"
operation="eq" value="sles236"/>
         </rule>
       </rsc_location>
       <rsc_location id="pref_location_drbd3" rsc="ms-drbd3">
         <rule id="sles236_location_drbd3" score="100"
boolean_op="and" role="Master">
           <expression attribute="#uname" id="drbd3_on_sles236"
operation="eq" value="sles236"/>
         </rule>

I think this is the cause. You prefer to run drbd on sles236.

       </rsc_location>
       <rsc_order id="drbd0_before_tr2_xen" from="xen_tr2"
action="start" to="ms-drbd0" to_action="promote"/>
       <rsc_order id="drbd1_before_tr2_xen" from="xen_tr2"
action="start" to="ms-drbd1" to_action="promote"/>
       <rsc_order id="drbd2_before_tr2_xen" from="xen_tr2"
action="start" to="ms-drbd2" to_action="promote"/>
       <rsc_order id="drbd3_before_tr2_xen" from="xen_tr2"
action="start" to="ms-drbd3" to_action="promote"/>
       <rsc_colocation id="col_xen_drbd0_master" from="xen_tr2"
from_role="Started" to="ms-drbd0" to_role="Master" score="INFINITY"/>
       <rsc_colocation id="col_xen_drbd1_master" from="xen_tr2"
from_role="Started" to="ms-drbd1" to_role="Master" score="INFINITY"/>
       <rsc_colocation id="col_xen_drbd2_master" from="xen_tr2"
from_role="Started" to="ms-drbd2" to_role="Master" score="INFINITY"/>
       <rsc_colocation id="col_xen_drbd3_master" from="xen_tr2"
from_role="Started" to="ms-drbd3" to_role="Master" score="INFINITY"/>
     </constraints>
   </configuration>
 </cib>

Regards
Dominik
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to