[Linux-HA] ocf:heartbeat:apache resource agent and timeouts
dg at doodle.com
Sun Apr 8 07:16:17 MDT 2012
On 05.04.2012 18:53, Lars Ellenberg wrote:
> Uhm, "invalid test case".
> rather try:
> iptables -I INPUT -p tcp --dport 80 -i lo -j REJECT
> or even
> iptables -I INPUT -p tcp --dport 80 -i lo -j REJECT --reject-with tcp-reset
Yes, then it works, but that's not surprising, because in this case the
operations return immediately and never time out. But why should a
non-responsive apache be an invalid test case? We've reached apache's
connection limit more than once, and from the client's point of view
this produces a very similar effect to '-j DROP'.
> Pacemaker behaviour is just the same,
> whether a monitor action "timed out", or "failed".
I've come to the conclusion that this just isn't true, please see my
other mail, I've listed all the steps I did in detail.
> After the monitor action timed out or failed,
> the recovery action by pacemaker would be to stop the service,
> and restart it (there or elsewhere).
> Did that not happen?
> The start operation of the apache RA internally does monitor as well,
> so it likely times out as well.
> I'd expect the cluster to move the unresponsive apache to some other
> node, after monitor and restart timed out. Which I think is the right
> thing to do.
I'm using unmanaged resources, because for our application there's no
point in having Pacemaker shut down apache (apache can be used on all
hosts in parallel and without restrictions). So no stop/start for us.
More information about the Linux-HA