JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 29

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 30

changes.mady.by.user Andreas Püschel

Saved on

Key

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

...

  • When terminating a job process, the Agent performs the following steps:
    • collect child process PIDs of job process recursively,
    • force termination of a job process and any child processes recursively.
  • The Agent makes use of Java for process management.

...

  • The Agent uses the kill_task.cmd script which is available from its var_<port>/work directory.
    • The script uses the taskkill command to force termination of the job's process and its childrenchild processes.
    • Download: kill_task.cmd
  • An individual script can be specified with a command line option on Agent startup, see JS7 - Agent Command Line Operation.

Termination of Agent

The follow applies to releases starting from 2.7.2.

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 in use job processes will forcibly be terminated. Orders for workflows related to affected jobs will be put set to the failed state.
  • Users are in control of failed orders that can be cancelled or resumed. Use of an Agent Cluster allows to resume orders without waiting for the terminated Subagent to be restarted.

...

  • Crash of the Agent is different to termination:
    • The Agent process is forcibly terminated, for example using the OS 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 set 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 set 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 AgentSubagent.

Resources

...