Discussion:
[Openais] stickiness='100' doesn't work
Anthem Cheng
2014-02-11 06:54:53 UTC
Permalink
Hello guys

I've set up a cluster recently with 2 RHEL 6.3 servers,
had corosync 1.4.1 and paemaker 1.1.7 installed.

the cluster is all fine but there is an issue with "stickiness='100'"
when I "standby" the node which has live resource, a floating IP, on it,
the floating IP can be brought up on the second one,
but if I "online" the standby node, the floating IP resource come back to
it again.

Also tried stop pacemaker and corosync on the node which has live resource,
I can see the resource be brought up on another one, but the same, if start
pacemaker and corosync, the resource failover back to original one again.


here is the conf:
[root at XXXXX XXXX]# crm configure show
node XXXXXX.XXXX.XXX.com \
attributes standby="on"
node XXXXX.XXXXX.XXXXX.com \
attributes standby="off"
primitive ClusterIP ocf:heartbeat:IPaddr2 \
params ip="10.87.192.10" cidr_netmask="24" \
op monitor interval="10s"
location cli-prefer-ClusterIP ClusterIP \
rule $id="cli-prefer-rule-ClusterIP" inf: #uname eq
XXXXXXX.XXXXX.XXXX.com
property $id="cib-bootstrap-options" \
dc-version="1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
no-quorum-policy="ignore"
rsc_defaults $id="rsc-options" \
resource-stickiness="100"


cannot find anything wrong, but it just doesn't work as expected.

thanks for any suggestion.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/openais/attachments/20140211/949b12c4/attachment.html>
Fabio M. Di Nitto
2014-04-07 03:39:53 UTC
Permalink
Post by Anthem Cheng
Hello guys
I've set up a cluster recently with 2 RHEL 6.3 servers,
had corosync 1.4.1 and paemaker 1.1.7 installed.
3 things:

1) wrong mailing list :) you want the pacemaker list
2) your packages are very old. we support pacemaker on RHEL starting
from 6.5, so please update first.
3) if the problem persists, then please file a ticket with Red Hat support.

Fabio
Post by Anthem Cheng
the cluster is all fine but there is an issue with "stickiness='100'"
when I "standby" the node which has live resource, a floating IP, on it,
the floating IP can be brought up on the second one,
but if I "online" the standby node, the floating IP resource come back
to it again.
Also tried stop pacemaker and corosync on the node which has live resource,
I can see the resource be brought up on another one, but the same, if
start pacemaker and corosync, the resource failover back to original one
again.
[root at XXXXX XXXX]# crm configure show
node XXXXXX.XXXX.XXX.com <http://XXXXXX.XXXX.XXX.com> \
attributes standby="on"
node XXXXX.XXXXX.XXXXX.com <http://XXXXX.XXXXX.XXXXX.com> \
attributes standby="off"
primitive ClusterIP ocf:heartbeat:IPaddr2 \
params ip="10.87.192.10" cidr_netmask="24" \
op monitor interval="10s"
location cli-prefer-ClusterIP ClusterIP \
rule $id="cli-prefer-rule-ClusterIP" inf: #uname eq
XXXXXXX.XXXXX.XXXX.com <http://XXXXXXX.XXXXX.XXXX.com>
property $id="cib-bootstrap-options" \
dc-version="1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14" \
cluster-infrastructure="openais" \
expected-quorum-votes="2" \
stonith-enabled="false" \
no-quorum-policy="ignore"
rsc_defaults $id="rsc-options" \
resource-stickiness="100"
cannot find anything wrong, but it just doesn't work as expected.
thanks for any suggestion.
_______________________________________________
Openais mailing list
Openais at lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/openais
Loading...