...
- The functions for terminating task processes for the JobScheduler Master and Universal Agent have been extended to allow the use of both SIGTERM and SIGKILL signals on Unix servers:
- SIGTERM is sent first and allows an orderly termination of task processes to take place within a limited period of time.
- If the time allowed has been exceeded and the processes are still running then SIGKILL will be sent.
- The information contained in this article draws together detailed information contained in a range of issues and should primarily be of interest to persons in engineering and to a lesser extent persons in operating functions.
Feature History
Display feature availability | ||
---|---|---|
|
Issues
Support of this feature is subject to the following issues:
...
- The use of both SIGTERM and SIGKILL signals on Unix servers has the following advantages:
The use of SIGTERM before SIGKILL means that there is a greater chance of data being saved after the signal has been issued.
The SIGTERM signal can - in contrast with SIGKILL - be monitored, i.e. a post-processing Script can be carried out.
- The implementation of SIGTERM allows post-processing methods such as
spooler_process_after()
.
The time allowed between the SIGTERM and SIGKILL signals can be specified in the command using the timeout attribute (the default is 15 sec):
<kill_task … timeout=".."/>
- This feature can also be applied for:
- remote processes, i.e. processes started by SSH and those started by an Agent,
- child processes started by a process running on an agent (
).Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1468
Implementation
JobScheduler Master
...