Number of monitor intervals to wait for resource to migrate after completing the migrate procedure. MigrateWaitLimit will be applicable for source as well as for target node; as the migrate operation brings the resource offline on the source node and online on the target node. We can also define MigrateWaitLimit as the number of monitor intervals required to wait for resource to go offline on source after completing the migrate procedure, and the number of monitor intervals to wait for resource to come online on target after the resource goes offline on source.

Default value is 2. The MigrateWaitLimit attribute can be overridden.

Probes fired manually are counted when MigrateWaitLimit is set and the resource is waiting to migrate. For example, if the MigrateWaitLimit of a resource is set to 5 and the MonitorInterval is set to 60 (seconds), the resource waits for a maximum of five monitor intervals (that is, 5 x 60), and if all five monitors within MigrateWaitLimit report the resource as online on source node, it sets the ADMIN_WAIT flag. If you run another probe, the resource waits for four monitor intervals (that is, 4 x 60), and if the fourth monitor does not report the state as offline on source , it sets the ADMIN_WAIT flag. This process is repated for remaining monitor intervals (3x60, 2x60 and 1x60). Similarly if the resource does not moved to online state within the MigrateWaitLimit then it sets the ADMIN_WAIT flag.