[Pacemaker] promote is delayed more than 60 sec after stonith reset

[Andrew Beekhof]

On Wed, Oct 14, 2009 at 2:48 AM, hj lee <kerdosa at gmail.com> wrote:
> Hi,
>
> I configured two nodes cluster on RHEL 5.3 with the following resources.
> Note that I am using pacemaker-1.0.6.
> - IPMI stonith as a clone. Each IPMI clone is monitoring the other node.
> - One Master/Slave resource: Master is running on node1, Slave is running on
> node2.
> - One FakeIPMI resource.
>
> When I manually trigger the failure in monitor and stop operation of
> FakeIPMI at node1, the IPMI stonith running on node2 detects its state
> unclean correctly and it tries to demote Master resource in node1 and reset
> th node1. The problem I am seeing is the promotion happens 60 sec later
> after the stonith reset the node1 successfully.
>
> I want the Slave gets promoted immediately right after the stonith reset
> returned successfully! From the log,

You mean the one we can't see or comment on?

> the promotion is started by demote
> operation timeout. Obviously the Master node is rebooting and the demote
> will get timeout. I think the demote operation should be cancelled when the
> stonith reset the node and the promotion should happen immediately from.
>
> Thanks
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>