[ClusterLabs] question about ocf metadata actions

[Kristoffer Grönlund]

he.hailong5 at zte.com.cn writes:

> Hi,
>
>
> Does the timeout configured in the ocf metadata actually take effect?
>
>
>
>
> ＜actions＞
>
>     ＜action name="start" timeout="300s" /＞
>
>     ＜action name="stop" timeout="200s" /＞
>
>     ＜action name="status" timeout="20s" /＞
>
>     ＜action name="monitor" depth="0" timeout="20s" interval="2s" /＞
>
>     ＜action name="meta-data" timeout="120s" /＞
>
>     ＜action name="validate-all"  timeout="20s" /＞
>
> ＜/actions＞
>
>
>
>
> what's the relationship with the ones configured using "crm configure primitive" ?

Hi Allen,

The timeouts in the OCF metadata are merely documentation hints, and
ignored by Pacemaker unless configured appropriately in the CIB (which
is what crm configure primitive does). See the OCF documentation:

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: Users at 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

-- 
// Kristoffer Grönlund
// kgronlund at suse.com