...

Termination of the Agent will consider terminating and restarting jobs as follows:

• For details see JS7 - Agent Command Line Operation, Stopping the Agent.
• Depending on command line options used job processes will forcibly be terminated. Orders for workflows related to affected jobs will be put to the failed state.
• Users are in control of failed orders that can be cancelled or resumed from some other Agent in . Use of an Agent Cluster allows to resume orders without waiting for the terminated Subagent to be restarted.

Crash of the Agent will consider termination of jobsterminating and restarting jobs as follows:

• Crash of the Agent is different to termination:
  • The Agent process is killed, for example using the command kill -9 <agent-pid> on Unix.
  • The JS7 - Agent Watchdog will terminate any running job processes. Orders for workflows related to affected jobs will be put to the blocked state.
• Crash of the machine or of the container the Agent is operated for will crash the Agent and any running jobs. Related orders will be put to the blocked state.
• Users have limited control of blocked orders as the Controller does not know the execution status.
  • Standalone Agents will restart crashed jobs on restart of the Agent unless jobs are marked being not restartable. No operations on blocked orders can be performed until the Standalone Agent is restarted.
  • Cluster Agents allow to confirm loss of a crashed Subagent. In this situation crashed jobs will be restarted from some other Subagent unless they are marked being not restartable. Users control if jobs will be restarted on restart of the crashed Subagent or if they should be restarted from some other Agent.

Resources

• JS7 - Agent Command Line Operation
• JS7 - Agent Watchdog