...
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 |
Each MC not in Failover mode can become top MC for Failover Tasks owned by |
other MCs as soon as no heartbeats are received from the remote MCs younger than 5 minutes. |
| MC01 |
- When MC00 is in Manual Failover, and MC01 is online
- When MC00 is in Manual Failover, and MC02 is online
| MC00, MC02, MC01 | |
| MC02 | MC00, MC01, MC02 |
| Status MC00 | Status MC01 | Status MC02 | Remarks |
|---|---|---|---|
| OK | OK | OK | Each MC runs its own Tasks. No Failover Tasks are taken over. |
| Failed over | OK | OK | MC01 runs additionally all Failover Task from MC00. MC00 will no longer run its own |
| "Suspend duty in Failover" |
| Tasks. | |||
| OK | Failed over | OK | MC00 runs additionally all Failover |
| Task from MC01. |
| MC01 will no longer run its |
| own " |
| Suspend duty in Failover" Tasks. | |||
| OK | OK | Failed over | No visible effect since MC02 does not own Failover Tasks. MC02 is not allowed to take over Failover tasks from other MCs. |
| Failed over | Failed over | OK | MC02 runs additionally all Failover Task from MC00 and MC01. MC00 and |
| MC01 will no longer run their own "Suspend duty in Failover" Tasks. | |||
| Failed over | OK | Failed over | MC01 |
| runs additionally all Failover Task from MC00. MC00 will no longer run its own "Suspend duty in Failover" Tasks. MC02 does not own Failover Tasks. MC02 is not allowed to take over Failover tasks from |
| other MCs. |
Failover MC02
| OK | Failed over | Failed over | MC00 runs additionally all Failover Task from MC01. MC01 will no longer run its own "Suspend duty in Failover" Tasks. MC02 is not allowed to take over Failover tasks from other MCs. |
| Failed over | Failed over | Failed over |