On Thu, Aug 11, 2011 at 10:56:15AM +0200, Ulrich Windl wrote:
> Hi!
>
> Sorry, if this has been discussed before, but I think ocf:heartbeat:Xen does
> not what the documentations says about timeout:
>
> <parameter name="shutdown_timeout">
> <longdesc lang="en">
> The Xen agent will first try an orderly shutdown using xm shutdown.
> Should this not succeed within this timeout, the agent will escalate to
> xm destroy, forcibly killing the node.
>
> If this is not set, it will default to two-third of the stop action
> timeout.
>
> Setting this value to 0 forces an immediate destroy.
> </longdesc>
>
> The code to set the timeout is this:
> if [ -n "$OCF_RESKEY_shutdown_timeout" ]; then
> timeout=$OCF_RESKEY_shutdown_timeout
> elif [ -n "$OCF_RESKEY_CRM_meta_timeout" ]; then
> # Allow 2/3 of the action timeout for the orderly shutdown
> # (The origin unit is ms, hence the conversion)
> timeout=$((OCF_RESKEY_CRM_meta_timeout/1500))
> else
> timeout=60
> fi
>
> The primitive was configured like this:
> primitive prm_v02_xen ocf:heartbeat:Xen params xmfile="/etc/xen/vm/v02" op
> start timeout="300" op stop timeout="300" op monitor interval="1200"
> timeout="90"
>
> So I'd expect 2/3rds of 300s to be 200s. However the syslog says:
> Aug 11 10:14:37 h01 Xen[25140]: INFO: Xen domain v02 will be stopped
> (timeout: 13s)
> Aug 11 10:14:50 h01 Xen[25140]: WARNING: Xen domain v02 will be destroyed!
>
> According to the code, that's printed here:
> if [ "$timeout" -gt 0 ]; then
> ocf_log info "Xen domain $dom will be stopped (timeout: ${timeout}s)"
>
> So I guess something is wrong.
There has been a pacemaker bug (or was it lrmd bug?) that caused the
stop action to be sometimes passed an incorrect *_CRM_meta_*
environment.
20000 / 1500 happens to end up being 13, so maybe somehow the timeout
used some default value of 20 seconds?
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
