[Pacemaker] still failure-timeout problems

Andrew Beekhof andrew at beekhof.net
Wed Mar 9 05:33:36 EST 2011


On Mon, Feb 28, 2011 at 1:54 PM, Klaus Darilion
<klaus.mailinglists at pernau.at> wrote:
> Hi!
>
> I still suffer the problem, that the fail-count is not cleared after
> failure-timeout.

This is a feature in 1.1 and not available in 1.0

> After the second failure of Kamailio the IP-address is
> moved to the other node, and restarted on the previous node after
> failure-timeout.
>
> But as the fail-count is not cleared, subsequent failures will cause
> immediate failover (instead of moving only after 2 failures).
>
> Is this by design? Or is it a bug?
>
> I am using pacemaker 1.0.9 (Debian backports)
>
> Thanks
> Klaus
>
> node armani \
>        attributes standby="off"
> node bulgari \
>        attributes standby="off"
> primitive failover-ip ocf:heartbeat:IPaddr \
>        params ip="83.136.32.161" \
>        op monitor interval="3s"
> primitive kamailio lsb:kamailio \
>        meta migration-threshold="2" failure-timeout="30" \
>        op monitor interval="10" timeout="10"
> clone cloneKamailio kamailio
> colocation colo_ip_with_kamailio inf: failover-ip cloneKamailio
> property $id="cib-bootstrap-options" \
>        dc-version="1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b" \
>        cluster-infrastructure="openais" \
>        expected-quorum-votes="2" \
>        stonith-enabled="false" \
>        no-quorum-policy="ignore" \
>        cluster-recheck-interval="5s"
> rsc_defaults $id="rsc-options" \
>        resource-stickiness="5"
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>




More information about the Pacemaker mailing list