[Pacemaker] Ressources not moving to node with better connectivity - pingd

Bauer, Stefan (IZLBW Extern) Stefan.Bauer at iz.bwl.de
Mon Dec 9 10:17:24 UTC 2013


Hi List,

even though following well known documentations about a ping clone resource my resources are not moving to the node with the better connectivity:

2 Nodes configured, 2 expected votes
6 Resources configured.
============

Online: [ debian6-n2 debian6-n1 ]

Resource Group: cluster1
     p_eth0     (ocf::heartbeat:IPaddr2):       Started debian6-n2
     p_alias0   (ocf::heartbeat:IPaddr2):       Started debian6-n2
     p_openvpn  (lsb:openvpn):  Started debian6-n2
     p_conntrackd       (lsb:conntrackd-sync):  Started debian6-n2
Clone Set: pingclone [p_ping]
     Started: [ debian6-n1 debian6-n2 ]

Node Attributes:
* Node debian6-n2:
    + pingd                             : 150           : Connectivity is degraded (Expected=300)
* Node debian6-n1:
    + pingd                             : 300

I would expect the resources to move to N1.
Resource-stickiness is set to 100.
2 Pinghosts are configured - n2 can right now only reach a single pinghost.

Resource              Score     Node       Stickiness #Fail    Migration-Threshold
p_alias0              700       debian6-n2 100        0
p_alias0              -INFINITY debian6-n1 100        0
p_conntrackd          100       debian6-n2 100        0
p_conntrackd          -INFINITY debian6-n1 100        0
p_eth0                1650      debian6-n2 100        0
p_eth0                300       debian6-n1 100        0
p_openvpn             300       debian6-n2 100        0
p_openvpn             -INFINITY debian6-n1 100        0
p_ping:0              100       debian6-n1 100        0
p_ping:0              -INFINITY debian6-n2 100        0
p_ping:1              0         debian6-n1 100        0
p_ping:1              100       debian6-n2 100        0

Anybody see what the problem could be?
To be honest I did not fully understood the deeper function of how the scores are calculated.

Thank you.

Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131209/73830697/attachment-0003.html>


More information about the Pacemaker mailing list