Configure the Pending Timeout for a Clustered Service or Application

Updated: October 24, 2008

Applies To: Windows Server 2008

You can adjust the pending timeout setting for a clustered service or application. This ensures that the Cluster service allows the appropriate amount of time for the application or service to start (during the process of moving or failing over the application or service). For example, if a particular application requires a relatively long time to start, you could increase the pending timeout.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).

  1. In the Failover Cluster Management snap-in, if the cluster you want to configure is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and select or specify the cluster you want.

  2. If the console tree is collapsed, expand the tree under the cluster that you want to configure.

  3. Expand Services and Applications.

  4. Click the clustered service or application that you want to configure the pending timeout for.

  5. In the center pane, right-click the resource for the service or application, click Properties, and then click the Policies tab.

  6. Under Pending timeout, specify the length of time, in minutes and seconds, that the resource can take to change states between Online and Offline before the Cluster service puts the resource in the Failed state.

    The default timeout value is 3 minutes.

  • To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

Community Additions

ADD
Show: