[Pacemaker] Adding a timeout to an existing primitive
Uwe Ritzschke
uwe.ritzschke.2 at cms.hu-berlin.de
Fri Feb 18 17:43:02 CET 2011
This will change the global timeouts. If you just want to change the
settings for one resource, type "crm configure edit" to edit your
configuration directly (and even without xml :-). Search your resource
and add the appropriate intervals- like this:
primitive PostgreSQL [...] \
op start interval="0" timeout="120" \
op stop interval="0" timeout="120"
cheers
Uwe
Am 18.02.2011 17:34, schrieb Jody McIntyre:
> On Fri, Feb 18, 2011 at 11:29 AM, Vadym Chepkov <vchepkov at gmail.com
> <mailto:vchepkov at gmail.com>> wrote:
>
> crm configure property default-action-timeout=120s
>
>
> Will that set the default for all primitives? I just want to change
> PostgreSQL.
>
> Alternately I could change the default but then I'd want to change
> ClusterIP to be something lower, which is essentially the same problem :)
>
> Cheers,
> Jody
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110218/37ce28ee/attachment-0001.htm>
More information about the Pacemaker
mailing list