3.1.5.3 IsAlive Timer Event

As specified in the ApiCreateResourceType method (see section 3.1.4.1.27 for protocol version 2, or section 3.1.4.2.27 for protocol version 3), the point in time when the server starts the IsAlive timer (section 3.1.2.3) is implementation specific, and the actions performed by the server when the IsAlive timer expires are implementation specific.

A server typically starts the IsAlive timer when the associated resource transitions into the ClusterResourceOnline state (see ApiGetResourceState: section 3.1.4.1.13 for protocol version 2, or section 3.1.4.2.13 for protocol version 3). The expiration time of the IsAlive timer is typically designated by the dwIsAlive parameter in the ApiCreateResourceType method or by other implementation-specific mechanisms. When the IsAlive timer expires, the server typically performs an implementation-specific in-depth health-check of the resource. If the health-check fails, the server typically performs implementation-specific actions to confirm or restore the health of the resource. If the health-check succeeds, the server typically reschedules the IsAlive timer for the same interval. If the resource transitions out of the ClusterResourceOnline state, then the server typically cancels the IsAlive timer.

Show: