On 2014-03-12T16:16:54, Karl Rößmann <[email protected]> wrote:
> >>primitive fkflmw ocf:heartbeat:Xen \
> >> meta target-role="Started" is-managed="true" allow-migrate="true" \
> >> op monitor interval="10" timeout="30" \
> >> op migrate_from interval="0" timeout="600" \
> >> op migrate_to interval="0" timeout="600" \
> >> params xmfile="/etc/xen/vm/fkflmw" shutdown_timeout="120"
> >
> >You need to set a >120s timeout for the stop operation too:
> > op stop timeout="150"
> >
> >> default-action-timeout="60s"
> >
> >Or set this to, say, 150s.
> can I do this while the resource (the xen VM) is running ?
Yes, changing the stop timeout should not have a negative impact on your
resource.
You can also check how the cluster would react:
# crm configure
crm(live)configure# edit
(Make all changes you want here)
crm(live)configure# simulate actions nograph
before you type "commit".
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Pacemaker mailing list: [email protected]
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
