3.1.5.2 LooksAlive Timer Event

As specified in the ApiCreateResoureType 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 LooksAlive timer (section 3.1.2.2) is implementation specific, and the actions performed by the server when the LooksAlive timer expires are implementation specific.

A server typically starts the LooksAlive 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 LooksAlive timer is typically designated by the dwLooksAlive parameter in the ApiCreateResourceType method or by other implementation-specific mechanisms. When the LooksAlive timer expires, the server typically performs an implementation-specific low-cost 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, then the server typically reschedules the LooksAlive timer for the same interval. If the resource transitions out of the ClusterResourceOnline state, then the server typically cancels the LooksAlive timer.

Show: