|
Specifies, in seconds, the longest time that the JMX client, the site, waits for the
invocation of an MBean-server method to return. If a method does not return by the end of the
timeout period, the client moves to its next set of instructions and reports the operation as timed
out. By default, a client waits indefinitely for a method to return. If the MBean server is unable
to complete an invocation, the JMX client will hang indefinitely. The timeout period is site-wide
and applies to operations on a per-cluster basis.
The timeout period applies to operations on a per-cluster basis. An operation with a local
scope times out if the operation is not completed after the specified Timeout
period.
An operation with a global scope consists of an action on the local cluster and an action on
the remote cluster. The local and remote actions are timed separately. So, an operation with a
global scope times out if the local operation is not completed after the specified timeout period or
if the remote operation is not completed after the specified timeout period.
For example, the following command is started with a local scope:
# geomg start -e local multigroup
If you set the Timeout property to 3000 seconds, the geomg
start command times out if the operation does not complete after 3000 seconds.
You can start the same command with a global scope as follows:
# geomg start -e global multigroup
If the Timeout property is set to 3000 seconds, the geomg
start command times out if the operation is not completed on the local cluster after 3000
seconds or if the operation is not completed on the remote cluster after 3000 seconds. If the local
action takes 1500 seconds and the remote action takes 1500 seconds, the operation is not timed
out.
The multigroup timeout value is an estimated value that is applied to some sub-operations. The
timeout value does not apply to the entire operation, so not every operation on a protection group
is timed against the timeout period. For example, the time taken to initialize the data structure
and to check for the precondition of the operation are not timed in the timeout period.
Tuning recommendations: This property is assigned at
creation and tunable at runtime.
Category: Optional
Default: 30 seconds
Minimum: 20 seconds
Maximum: 3600 seconds
|