Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Current Situation
- The JOC Cockpit Cluster Service writes heartbeats to the database that are used to determine availability of the active JOC Cockpit instance.
- Heartbeats are written to the database using the database server clock. When checking if heartbeats are exceeded then JOC Cockpit compares using its local server clock.
- When the clocks of database server and JOC Cockpit server are not in sync then the JOC Cockpit Dashboard view indicates the connection status to the database being unstable/unhealthy. Users should keep the clocks of their servers in sync.
Desired Behavior
- JOC Cockpit makes use of the database server's clock exclusively when comparing heartbeats. No unstable/unhealthy connection status is reported if the clocks of database server and JOC Cockpit server are not in sync.
- Users should synchronize their servers from a time service as otherwise timestamps displayed will not be accurate.