Linux – Corosync with Pacemaker Resource explanation

centos6corosynclinuxpacemaker

I have the following resource:


primitive WowzaMediaServer lsb:WowzaMediaServer \
        op monitor interval="30s" timeout="60" \
        op start interval="0" timeout="60" \
        op stop interval="0"

I would like to understand what does "monitor Interval" and "timeout" mean.

Best Answer

This means:

Monitor (i.e. check its status) the lsb service WowzaMediaServer every 30 seconds and timeout after 60 seconds.

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Clusters_from_Scratch/_adding_a_resource.html

Related Solutions

Pacemaker/corosync timeout before resource transfers

It sounds like migration-threshold is what you're looking for.

Assumming that you have a resource which is setting op monitor interval to 20s:

primitive p_foo ocf:heartbeat:foo \
    params ...
    op monitor interval="20s"

and you want it doesn't migrate to a new node within 1 minute, so you should set migration-threshold to 3:

primitive p_foo ocf:heartbeat:foo \
    params ...
    op monitor interval="20s"
    meta target-role="Started" migration-threshold="3"

Pacemaker – stop a resource which was started on another node

If I understand you correctly, you want to keep the oldest instance running if pacemaker detects that more than one is running. This is not possible with pacemaker and I'm not sure if you could detect reliably "the oldest process" at all, think about service restarts for example. So the closest you can implement with current pacemaker is the "multiple_active" option you already mentioned.

Best Answer

Related Solutions

Pacemaker/corosync timeout before resource transfers

Pacemaker – stop a resource which was started on another node

Related Topic