[Pacemaker] Manual promote/demote and time between demote and promote

Andrew Beekhof andrew at beekhof.net
Tue Jul 28 04:26:29 EDT 2009

On Mon, Jul 20, 2009 at 8:04 PM, hj lee<kerdosa at gmail.com> wrote:
> Hi,
> I am building a simple multi-state clone with max-master=2. The
> demote/promote is working OK by using migration-threshold or co-location
> constraint. But I have two questions:
> 1. Except these two methods, is there any way to invoke demote/promote
> manually just for testing?

You can set target-role=Slave to prevent it from being promoted.
Or you can use crm_master to manually tweak the promotion scores.

> 2. By using co-location constraint, the time takes from demote to promote is
> around 3 sec(when notify is enabled) and 1 sec (when notify is disabled).
> For mission critical application, I think a downtime of 1 or 3 sec is too
> long. How can I minimize this transition time?

Its purely down to your network and what the resource is doing during
the promote/demote and notify actions.

More information about the Pacemaker mailing list