...
MC | Failover priorities order (ordered highest rank to lowest rank) | Example |
---|---|---|
MC00 | MC01< MC02 < MC00 | Three Master Controllers in a single synchronization pool with:
Each MC that is not in Failover mode can become top MC for Failover Tasks owned by other MCs as soon as no recent heartbeats (5 minutes threshold) are received from higher ordered remote MCs. |
MC01 | 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 no longer 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 is no longer allowed to take over Failover tasks from other MCs. |
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 no longer allowed to take over Failover tasks from other MCs. |
Failed over | Failed over | Failed over | MC00 and MC01 will run their own "Suspend duty in Failover" Tasks since each MC has become the top MC for their own Failover Tasks. The MCs are no longer allowed to take over Failover tasks from other MCs. |