Page History

...

Primary and Secondary Controller instances require a dedicated Standalone Agent to be available that acts as an arbitrator in case of fail-over and switch-over.

Start-up of Controller Cluster

...

• The Cluster Watch Agent knows immediately when the Active Controller Instance is down due to a connection loss from this instance.
• The Standby Controller Instance holds a connection to the Active Controller Instance and knows immediately when this connection is lost.
• Failure of the Active Controller Instance is the point in time when the Standby Controller Instance and the Cluster Watch Agent check to find common ground about a cluster fail-over operation: They determine if they should declare the Active Controller Instance being inoperable and after a short period of 1-2s they proceed and cast their votes if the Standby Controller Instance should now become the Active Controller Instance.
• As a prerequisite for fail-over both the Cluster Watch Agent and the Standby Controller Instance have to confirm that the Standby Controller Instance's journal was in sync with the Active Controller Instance at the point in time of failure.

...

• In the JS7 - Dashboard the user performs one of the operations: 
  • Active Controller Instance action menu: Abort Terminate -> With failswitch-over
  • Active Controller Instance action menu:Abort Terminate and restart -> With failswitch-over

No switch-over occurs when

...