...
As a rule, any Master Controller is in charge of running its own tasks. In addition, it takes over Failover tasks for which the owner is not visibly producing heartbeats indicating its health, and where no other healthy Master Controllers with better failover priority (lower value) are available. Each Master Controller has its own list of failover priorities, deciding which Master Controller becomes the next top MC in a Failover situation. For best behaviour, it is recommended to list all Master Controllers that are visible in the list of Failover Priorities. In order to prevent the local Master Controller becoming the top Master Controller for taking over its own "Suspend duty in Failover" Tasks in case of a manual failover, it is common to specify all other Master Controllers first, and put the local Master Controllers' Failover Priority last.
Example: Three Master Controllers in a single synchronization pool with MC00 and MC01 owning failover tasks, MC02 has to take over when MC00 or MC01 are gone but MC02 is not owning any Failover Tasks.
| MC | Failover priorities order (ordered highest rank to lowest rank) | Remarks |
|---|---|---|
| MC00 | MC01, MC02, MC00 | MC00 becomes top MC for Failover Tasks owned by MC01 when MC00 has received no MC01 and MC02 heartbeats younger than 5 minutes.
nd MC01 is offline, MC02 will run the "Suspend duty in Failover" from MC00 and all Failover Tasks from MC01. MC00 will run its Run "Run duty" tasks and "Run Duty and Failover" Tasks. |
| MC01 | MC00, MC02, MC01 | MC00 takes over Failover tasks from MC00 when MC01 is down. |
| MC02 | MC00, MC01, MC02 |
| Master Controller | Failover MC00 | Failover MC01 | Failover MC02 | MC02 | |
|---|---|---|---|---|---|