このコンテンツは選択した言語では利用できません。
E.2. Enforcing Resource Timeouts
There is no timeout for starting, stopping, or failing over resources. Some resources take an indeterminately long amount of time to start or stop. Unfortunately, a failure to stop (including a timeout) renders the service inoperable (failed state). You can, if desired, turn on timeout enforcement on each resource in a service individually by adding
__enforce_timeouts="1"
to the reference in the cluster.conf
file.
The following example shows a cluster service that has been configured with the
__enforce_timeouts
attribute set for the netfs
resource. With this attribute set, then if it takes more than 30 seconds to unmount the NFS file system during a recovery process the operation will time out, causing the service to enter the failed state.