[ClusterLabs] Antw: Unexpected Resource movement after failover

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Thu Oct 13 14:15:48 UTC 2016


Hi!

Don't you need 10 constraints, excluding every possible pair of your 5 resources (named A-E here), like in this table (produced with R):

     [,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] [,9] [,10]
[1,] "A"  "A"  "A"  "A"  "B"  "B"  "B"  "C"  "C"  "D"  
[2,] "B"  "C"  "D"  "E"  "C"  "D"  "E"  "D"  "E"  "E"  

Ulrich

>>> Nikhil Utane <nikhil.subscribed at gmail.com> schrieb am 13.10.2016 um 15:59 in
Nachricht
<CAGNWmJW0CWMr3bvR3L9xZCAcJUzyczQbZEzUzpaJxi+Pn7Oj_A at mail.gmail.com>:
> Hi,
> 
> I have 5 nodes and 4 resources configured.
> I have configured constraint such that no two resources can be co-located.
> I brought down a node (which happened to be DC). I was expecting the
> resource on the failed node would be migrated to the 5th waiting node (that
> is not running any resource).
> However what happened was the failed node resource was started on another
> active node (after stopping it's existing resource) and that node's
> resource was moved to the waiting node.
> 
> What could I be doing wrong?
> 
> <nvpair id="cib-bootstrap-options-have-watchdog" value="true"
> name="have-watchdog"/>
> <nvpair id="cib-bootstrap-options-dc-version" value="1.1.14-5a6cdd1"
> name="dc-version"/>
> <nvpair id="cib-bootstrap-options-cluster-infrastructure" value="corosync"
> name="cluster-infrastructure"/>
> <nvpair id="cib-bootstrap-options-stonith-enabled" value="false"
> name="stonith-enabled"/>
> <nvpair id="cib-bootstrap-options-no-quorum-policy" value="ignore"
> name="no-quorum-policy"/>
> <nvpair id="cib-bootstrap-options-default-action-timeout" value="240"
> name="default-action-timeout"/>
> <nvpair id="cib-bootstrap-options-symmetric-cluster" value="false"
> name="symmetric-cluster"/>
> 
> # pcs constraint
> Location Constraints:
>   Resource: cu_2
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
>   Resource: cu_3
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
>   Resource: cu_4
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
>   Resource: cu_5
>     Enabled on: Redun_CU4_Wb30 (score:0)
>     Enabled on: Redund_CU2_WB30 (score:0)
>     Enabled on: Redund_CU3_WB30 (score:0)
>     Enabled on: Redund_CU5_WB30 (score:0)
>     Enabled on: Redund_CU1_WB30 (score:0)
> Ordering Constraints:
> Colocation Constraints:
>   cu_3 with cu_2 (score:-INFINITY)
>   cu_4 with cu_2 (score:-INFINITY)
>   cu_4 with cu_3 (score:-INFINITY)
>   cu_5 with cu_2 (score:-INFINITY)
>   cu_5 with cu_3 (score:-INFINITY)
>   cu_5 with cu_4 (score:-INFINITY)
> 
> -Thanks
> Nikhil








More information about the Users mailing list