[Pacemaker] Adding a timeout to an existing primitive

[Vadym Chepkov]

On Fri, Feb 18, 2011 at 11:17 AM, Jody McIntyre <jodym at trustcentric.com> wrote:
> I added a primitive to my cluster without setting a timeout:
>
> root at trustcentric2:~# crm configure primitive PostgreSQL
> ocf:trustcentric:postgresql
> WARNING: PostgreSQL: default timeout 20s for start is smaller than the
> advised 120
> WARNING: PostgreSQL: default timeout 20s for stop is smaller than the
> advised 120
>
> I would now like to correct the timeout, since the defaults are too short.
> How do I do this?  I found a brief section in one of the manuals:
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html#s-operation-timeouts
> but this is really unclear.  What id do I use in the <op>?  Can I simply
> make one up?  I assume the name attribute matches the command in the OCF but
> I'm not sure.


crm configure property default-action-timeout=120s

Cheers,
Vadym

>
> Also, perhaps more importantly, is there a way to do this without editing
> XML?  I am happy to do this myself, but I don't think in-depth knowledge of
> XML should be a requirement for any admins we hire!
>
> I have attached an XML dump.
>
> Thanks,
> 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
>
>