PendingTimeout
Sets the number of milliseconds that a Resource Monitor will wait for a resource DLL to update the status of a resource in an OnlinePending or OfflinePending state before terminating the resource. The following table summarizes the attributes of the PendingTimeout property.
| Attribute | Value |
|---|---|
| Data type | DWORD |
| Access | Read/write |
| Structure | CLUSPROP_DWORD |
| Minimum | 10 |
| Maximum | 0xFFFFFFFF |
| Default | 180000 |
Remarks
The PendingTimeout property does not necessarily limit the time that a resource can spend in a ClusterOnlinePending or ClusterOfflinePending state. This property determines only how long a Resource Monitor will wait for resource DLLs to report status updates with the SetResourceStatus function. As long as a resource DLL never exceeds the PendingTimeout interval between calls to SetResourceStatus, the resource DLL can keep a resource in a pending state indefinitely.
If a resource DLL exceeds the PendingTimeout interval between calls to SetResourceStatus, the Resource Monitor calls the resource DLL's Terminate entry point function.
Note that the PendingTimeout property cannot be greater than the DeadlockTimeout property – the lower of the two values will be used to determine if the resource should be online. When debugging cluster resources, both values should be incremented for the debugging session.
Examples
The property value portion of a property list entry for PendingTimeout can be set with the following example code:
DWORD PendingTimeoutData = 120000;
CLUSPROP_DWORD PendingTimeoutValue;
PendingTimeoutValue.Syntax.dw = CLUSPROP_SYNTAX_LIST_VALUE_DWORD;
PendingTimeoutValue.cbLength = sizeof(DWORD);
PendingTimeoutValue.dw = PendingTimeoutData;
Requirements
| Minimum supported client |
None supported |
| Minimum supported server |
Windows Server 2008 Enterprise, Windows Server 2008 Datacenter |