You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Purpose

  • The Cluster Service is used to operate a passive cluster of JOC Cockpit instances and to perform fail-over operations and switch-over operations between cluster members.
  • Any other JS7 - Services depend on the Cluster Service in order to be started for the active JOC Cockpit instance.

Fail-over

Any running JOC Cockpit instances connected to the same JS7 - Database implement a passive cluster. The active cluster member runs the Cluster Service, any passive cluster members watch for the active cluster members' ongoing operation by checking its heartbeats. In case of failure of the active cluster member one of the passive cluster members will become active and will start its Cluster Service.

Switch-over

The switch-over operation is technically similar to the fail-over operation, however, switch-over is caused by the GUI or the API and allows the Cluster Service to normally stop any running services.

Configuration

Location

  • The "Settings" menu is available from the JOC Cockpit GUI.

Configuration Items

SectionSettingDefaultRequiredPurpose





Logging

  • The Cluster Service logs general messages, warnings and errors to the joc.log file.
  • More detailed information in addition is logged to the Main Log service-cluster.log file.
  • In addition to the Main Log detailed debug information is logged to the Debug Log service-cluster-debug.log file.
  • For details see JS7 - Log Files and Locations


  • No labels