JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 6

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 7

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • An outage of the Controller does not necessarily affect the execution of workflows by Agents. Agents will continue to execute workflows. However, if a workflow includes jobs that are executed on different Agents then the workflow will be put on hold as the Controller is required to switch Agents during execution of the workflow.

  • The Controller holds any all workflow-related configuration items and orchestrates Agents. At design-time Agents receive the workflow configuration from the Controller and at run-time Agents return execution results and JS7 - Order State Transitions to the Controller.
  • The Controller passes execution results to the JS7 - History Service that which updates the JOC Cockpit database.
  • If no a connection from a Controller is not available then:
    • Agents will act autonomously. Execution results are stored with in the Agents' journal.
    •  JOC  The JOC Cockpit will not be updated from with workflow execution results.
  • Testing by SOS includes to perform performing tests for the scenario when the Controller is not available for 24 hours and the Agent executes all scheduled orders. When the Controller is started again then job execution results are updated to the JOC Cockpit history and become visible with in the GUI.

JOC Cockpit Behavior

  • Users do not receive up-to-date information:
    • The JOC Cockpit will not receive updated information about the state of orders and of workflow execution results.
    • The GUI will report the Controller being unreachable and has will have no information about the status of Agents.
  • Any interaction with a Controller such as to deploy deploying workflows and to cancelcancelling/suspend suspending orders is will be delayed.
    • This means that such requests are held in memory with the JOC Cockpit Proxy Service that which will try to forward the requests when the Controller becomes available.
    • It is not recommended to restart that the JOC Cockpit is restarted in this situation as pending requests would be lost and deployments would have to be repeated.
  • The JOC Cockpit Proxy Service will try to re-establish the connection to the Controller. When this is successful then the GUI will automatically updates the status of the Controller with in its Dashboard.

Agent Behavior

  • Workflows are deployed to Agents just once - at design-time. At run-time, when the Agent receives will have received orders for workflows some time, such as a week, in advance, e.g. a week ahead by . These orders come from the JS7 - Daily Plan Service, then it and the agent can execute them autonomously.
  • In case of a Controller outage:
    • Agents will continue to execute workflows for at the scheduled date and time. 
    • the Agent's journal will grow. The journal holds execution results of for workflows and order state transitions.
  • Depending on the workflow load of workflows , the journal files that are stored with the ./state directory can grow to some Gigabytes. There is no harm about in this as long as sufficient storage is available.
  • When the connection between Controller and Agent becomes available then the Agent will report back order state transitions and execution results to the Controller and the Agent's journal will shrink.

...