...
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:
| MC | Failover priorities order (ordered highest rank to lowest rank) | Example |
|---|---|---|
| MC00 | MC01, MC02, MC00 | Three Master Controllers in a single synchronization pool with:
|
...
| MC00 | MC01, MC02, MC00 |
|
| MC | Failover priorities order (ordered highest rank to lowest rank) | Remarks |
|---|---|---|
Each MC that is not in Failover mode can become top MC for Failover Tasks owned by other MCs as soon as as no recent heartbeats (5 minutes threshold) are received from the higher ordered remote MCs younger than 5 minutes. | ||
| MC01 | MC00, MC02, MC01 | |
| MC02 | MC00, MC01, MC02 |
...