On Fri, Mar 31, 2017 at 09:46:18AM +0200, Kristoffer Grönlund wrote: > Ulrich Windl <[email protected]> writes: > > > I thought the hierarchy is like this: > > 1) default timeout > > 2) RA's default timeout > > 3) user-specified timeout > > > > So crm would go from 1) to 3) taking the last value it finds. Isn't it like > > that? > > No, step 2) is not taken by crm.
There's a command in crmsh to insert default timeouts in the resource. There was some initiative to do that at the resource creation time, i.e. that crmsh automatically propagates all defaults from the RA metadata, but that would've made the configuration very large. > > I mean if there's no timeout in the resource cnfiguration, doesn't the RM > > use > > the default timeout? > > Yes, it then uses the timeout defined in op_defaults: > > http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-operation-defaults At any rate, the RA metadata is only for informational purpose. Thanks, Dejan > > Cheers, > Kristoffer > > > > > Regards, > > Ulrich > > > >> > >> https://github.com/ClusterLabs/resource-agents/blob/master/doc/dev-guides/ra > > > >> -dev-guide.asc#_metadata > >> > >>> Every action should list its own timeout value. This is a hint to the > >>> user what minimal timeout should be configured for the action. This is > >>> meant to cater for the fact that some resources are quick to start and > >>> stop (IP addresses or filesystems, for example), some may take several > >>> minutes to do so (such as databases). > >> > >>> In addition, recurring actions (such as monitor) should also specify a > >>> recommended minimum interval, which is the time between two > >>> consecutive invocations of the same action. Like timeout, this value > >>> does not constitute a default— it is merely a hint for the user which > >>> action interval to configure, at minimum. > >> > >> Cheers, > >> Kristoffer > >> > >>> > >>> Br, > >>> > >>> Allen > >>> _______________________________________________ > >>> Users mailing list: [email protected] > >>> http://lists.clusterlabs.org/mailman/listinfo/users > >>> > >>> Project Home: http://www.clusterlabs.org > >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > >>> Bugs: http://bugs.clusterlabs.org > >> > >> -- > >> // Kristoffer Grönlund > >> // [email protected] > >> > >> _______________________________________________ > >> Users mailing list: [email protected] > >> http://lists.clusterlabs.org/mailman/listinfo/users > >> > >> Project Home: http://www.clusterlabs.org > >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > >> Bugs: http://bugs.clusterlabs.org > > > > > > > > > > _______________________________________________ > > Users mailing list: [email protected] > > http://lists.clusterlabs.org/mailman/listinfo/users > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: http://bugs.clusterlabs.org > > -- > // Kristoffer Grönlund > // [email protected] > > _______________________________________________ > Users mailing list: [email protected] > http://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Users mailing list: [email protected] http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
