Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.8.1
-
None
-
None
Description
Current Situation :
In certain JOC Cockpit fail-over/switch-over scenarios, job execution on the Agents continues while processing of events by the JOC Cockpit History Service is temporarily interrupted or delayed. Consequently, the execution status of completed jobs is not immediately reflected in the JOC Cockpit history, resulting in incomplete or outdated information for the affected orders.
After the JOC Cockpit switch-over/recovery, the pending history events are processed and the order history is updated with the execution information received from the Controller. During the recovery and synchronization phase, for the configured jobs the Monitoring Service processes the affected orders based on the available history information and generates "Job runs longer than the expected duration" warnings for jobs that have already completed within the configured duration.
Desired Behaviour :
After JOC Cockpit fail-over and history synchronization, the Monitoring Service should correctly recognize the current execution status and duration of affected jobs and should not generate unexpected warnings for jobs that have already completed within the configured limit.
Attachments
Issue Links
- is related to
-
JOC-2267 History Service stops while replaying history events after JOC Cockpit fail-over
-
- Released
-