[Pacemaker] Booth ticket renovation timeout

Jorge Lopes jmclopes at gmail.com
Sun Feb 8 14:06:13 EST 2015

Hi all,

I'm performing a lab test were I have a geo cluster and an arbitrator, in a
configuration for disaster recovery with fail over. There are two main
sites (primary and disaster recovery) and a third site for arbitrator.

I have defined a ticket named "Primary", which will define which is the
primary site and which is the recovery site.
In my first configuration I had in the bothh.conf a value of 60  for the
ticket renewal. After I assigned the ticket to the primary site, when the
renovation time was reached, the ticket was not renewed and it ended up not
assigned to any of the sites.

So, I increased the value to 120 and now the ticket gets correctly renewed.

I am interested to know if there are any kind of constraints for the
minimum value for the ticket renewal. Is there any design aspect that would
recommend higher values? And what about in a production environment, where
time lags might be larger, would such a situation occur? What would be a
typical set of timeout values (please notice the CIB timeout values).

My configurations are as follow.

Thanks in advance,



crm configure show:
node $id="1084798152" cluster1-node1
primitive booth ocf:pacemaker:booth-site \
        meta resource-stickiness="INFINITY" \
        op monitor interval="10s" timeout="20s"
primitive booth-ip ocf:heartbeat:IPaddr2 \
        params ip=""
primitive dummy-pgsql ocf:pacemaker:Stateful \
        op monitor interval="15" role="Slave" timeout="60s" \
        op monitor interval="30" role="Master" timeout="60s"
primitive oversee-ip ocf:heartbeat:IPaddr2 \
        params ip=""
group g-booth booth-ip booth
ms ms_dummy_pqsql dummy-pgsql \
        meta target-role="Master" clone-max="1"
order order-booth-oversee-ip inf: g-booth oversee-ip
rsc_ticket ms_dummy_pgsql_primary primary: ms_dummy_pqsql:Master
rsc_ticket oversee-ip-req-primary primary: oversee-ip loss-policy=stop
property $id="cib-bootstrap-options" \
        dc-version="1.1.10-42f2063" \
        cluster-infrastructure="corosync" \
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20150208/c76bc5df/attachment-0002.html>

More information about the Pacemaker mailing list