[Pacemaker] default timeout for op start/stop

Dejan Muhamedagic dejanmm at fastmail.fm
Mon Sep 27 06:17:21 EDT 2010


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.

Thanks,

Dejan

> 
> Regards,
> Pavlos

> _______________________________________________
> 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





More information about the Pacemaker mailing list