Re: [ClusterLabs] from where does the default value for start/stop op of a resource come ?
"Lentes, Bernd" writes: > Hi, > > i'm wondering from where the default values for operations of a resource come > from. [snip] > > Is it hardcoded ? All timeouts i found in my config were explicitly related > to a dedicated resource. > What are the values for the hardcoded defaults ? > > Does that also mean that what the description of the RA says as "default" > isn't a default, but just a recommendation ? The default timeout is set by the default-action-timeout property, and the default value is 20s. You are correct, the timeout values defined in the resource agent are not used automatically. They are recommended minimums, and the thought as I understand it (this predates my involvement in HA) is that any timeouts need to be reviewed carefully by the administrator. I agree that it is somewhat surprising. Cheers, Kristoffer -- // Kristoffer Grönlund // kgronl...@suse.com ___ Users mailing list: Users@clusterlabs.org 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
[ClusterLabs] from where does the default value for start/stop op of a resource come ?
Hi, i'm wondering from where the default values for operations of a resource come from. I tried to configure: crm(live)# configure primitive prim_drbd_idcc_devel ocf:linbit:drbd params drbd_resource=idcc-devel \ > op monitor interval=60 WARNING: prim_drbd_idcc_devel: default timeout 20s for start is smaller than the advised 240 WARNING: prim_drbd_idcc_devel: default timeout 20s for stop is smaller than the advised 100 WARNING: prim_drbd_idcc_devel: action monitor not advertised in meta-data, it may not be supported by the RA from where come the default timeout of 20 sec ? My config does not have it in his op_default section: Is it hardcoded ? All timeouts i found in my config were explicitly related to a dedicated resource. What are the values for the hardcoded defaults ? Does that also mean that what the description of the RA says as "default" isn't a default, but just a recommendation ? crm(live)# ra info ocf:linbit:drbd ... Operations' defaults (advisory minimum): start timeout=240 promote timeout=90 demotetimeout=90 notifytimeout=90 stop timeout=100 monitor_Slave timeout=20 interval=20 monitor_Master timeout=20 interval=10 is not implemented by default ? Is it explicitly necessary to configure start/stop operations and related timeouts ? What if i don't do that ? I use default values i don't know ? Bernd -- Bernd Lentes Systemadministration institute of developmental genetics Gebäude 35.34 - Raum 208 HelmholtzZentrum München bernd.len...@helmholtz-muenchen.de phone: +49 (0)89 3187 1241 fax: +49 (0)89 3187 2294 no backup - no mercy Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Heinrich Bassler, Dr. Alfons Enhsen Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671 ___ Users mailing list: Users@clusterlabs.org 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