Page History
...
- the Agent is not running, for example after a crash.
- In case of Agent crash the JS7 - Agent Watchdog will terminate running jobs provided that the Watchdog is active.
- the Agent continues to run, but no connection can be established, for example in case of network errors.
...
For the time that an Agent is unreachable related orders are set to the blocked state. No operation is available on such orders until the Agent can be reached.
Restart Jobs from next Subagent after
...
Reset
In an Agent Cluster in case that a Subagent becomes unreachable users find the operation to reset the Subagent. This will cause jobs to be restarted from the next Subagent.
- The Manage Controllers/Agents page offers the Reset operation on individual Subagents. The Director Agent will consider this information and will restart jobs from the next Subagent.
- Note: The Reset operation has to be applied to the related, unreachable Subagent, not to the Director Agent.
- The operation should be handled with care as it can cause double job execution if the unreachable Subagent is still running the job. Before using the Reset operation users should verify that the Subagent is not running.
- Jobs that must exclude the risk of double job execution can be exempted from restart if they are marked not being restartable:
Jira server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-2151 Jira server SOS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1891 - Selection of the next Subagent is based on the type of Subagent Cluster, for example fixed-priority or round-robin.
Resources
Overview
Content Tools