[Pacemaker] default timeout for op start/stop

Pavlos Parissis pavlos.parissis at gmail.com
Mon Sep 27 11:44:48 UTC 2010


On 27 September 2010 12:17, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:

> Hi,
>
> On Mon, Sep 27, 2010 at 12:00:19PM +0200, Pavlos Parissis wrote:
> > On 24 September 2010 18:12, Dejan Muhamedagic <dejanmm at fastmail.fm>
> wrote:
> > [...snip...]
> >
> > > >
> > > > Default timeout is coded into the resource agent. You safely can
> ignore
> > > the
> > > > WARNINGs. These are also removed from more recent versions of
> pacemaker.
> > >
> > >
> > > These warnings shouldn't be ignored. The defaults which are coded
> > > in the RA are what the author of the RA advised as minimum. These
> > > values are, however, not used automatically by the CRM, so they
> > > need to be specified in the configuration. And then the resources
> > > should be thoroughly tested to see if the timeouts are meaningful
> > > in the given environment.
> > >
> > > Thanks,
> > >
> > Are you saying that if timeouts are not set CRM will wait for ever for
> each
> > operation to finish?
>
> No. It will use the global default timeout value
> (default-action-timeout) which is set to 20s. That's why the
> shell issues the warnings: 20s is shorter than what has been
> advertised in the meta-data of the RA you want to configure.
>

ok thanks
Pavlos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100927/796f511f/attachment-0002.htm>


More information about the Pacemaker mailing list