There are two different scenarios for restarting VM’s in case of slave Esxi FAILURE: one where heartbeat datastores are configured and one where heartbeat datastores are not configured.

The timeline is as follows:

• T0 – Slave failure
• T3s – Master begins MONITORING datastore heartbeats for 15 seconds.
• T10s – The host is declared unreachable and the master will ping the management NETWORK of the failed host. This is a continuous ping for 5 seconds.
• T15s – If no heartbeat datastores are configured, the host will be declared dead.
• T18s – If heartbeat datastores are configured, the host will be declared dead.
• The master monitors the network heartbeats of a slave. When the slave fails, these heartbeats will no longer be received by the master. We have defined this as T0. After 3 seconds (T3s), the master will start monitoring for datastore heartbeats and it will do this for 15 seconds. On the 10th second (T10s), when no network or datastore heartbeats have been detected, the host will be declared as “unreachable”.
• The master will also start pinging the management network of the failed host at the 10th second and it will do so for 5 seconds. If no heartbeat datastores were configured, the host will be declared “dead” at the 15th second (T15s) and VM restarts will be INITIATED by the master.
• If heartbeat datastores have been configured, the host will be declared dead at the 18th second (T18s) and restarts will be initiated.

There are two different scenarios for restarting VM’s in case of slave Esxi failure: one where heartbeat datastores are configured and one where heartbeat datastores are not configured.

The timeline is as follows: