Page History
...
Primary and Secondary Controller instances require JOC Cockpit or an Agent to act as Cluster Watch, i.e. as an arbitrator in case of fail-over and switch-over.
...
- The Active Controller Instance is killed, for example:
- on Unix with a SIGKILL signal corresponding to the command:
kill -9
- on Windows with the command:
taskkill /F
- on Unix with a SIGKILL signal corresponding to the command:
- The operating system crashes.
- In the JS7 - Dashboard the user performs one of the operations:
- Active Controller Instance action menu: Abort -> With fail-over
- Active Controller Instance action menu:Abort and restart -> With fail-over
- From the command line the user performs one of the operations:
controller_instance.sh | .cmd abort
Fail-over will not occur when:
- the Active Controller Instance is stopped normally from the command line:
controller_instance.sh | .cmd stop
- the Active Controller Instance is restarted normally from the command line:
controller_instance.sh | .cmd restart
- the operating system is shut down and
systemd
/init.d
or a Windows Service are in place to stop the Controller normally.
...
- In the JS7 - Dashboard the user performs one of the operations:
- Active Controller Instance action menu: Terminate -> With switch-over
- Active Controller Instance action menu:Terminate and restart -> With switch-over
- Cluster action menu: Switch-over
- From the command line the user performs the operation:
controller_instance.sh | .cmd switch-over
Switch-over will not occur when:
- the Active Controller Instance is stopped normally from the command line:
controller_instance.sh | .cmd stop
- the Active Controller Instance is restarted normally from the command line:
controller_instance.sh | .cmd restart
- the operating system is shut down and
systemd
/init.d
or a Windows Service are in place to stop the Controller normally.
...
Overview
Content Tools