LSF Version 7.3 - Administering Platform LSF

Default Job Control Actions
584 Administering Platform LSF
◆ SIGTSTP for parallel or interactive jobs. SIGTSTP is caught by the master
process and passed to all the slave processes running on other hosts.
◆ SIGSTOP for sequential jobs. SIGSTOP cannot be caught by user programs.
The SIGSTOP signal can be configured with the LSB_SIGSTOP parameter in
lsf.conf.
LSF invokes the SUSPEND action when:
◆ The user or LSF administrator issues a bstop or bkill command to the job
◆ Load conditions on the execution host satisfy any of:
❖ The suspend conditions of the queue, as specified by the STOP_COND
parameter in
lsb.queues
❖ The scheduling thresholds of the queue or the execution host
◆ The run window of the queue closes
◆ The job is preempted by a higher priority job
RESUME action
Change a suspended job from SSUSP, USUSP, or PSUSP state to the RUN state. The
default action is to send the signal SIGCONT.
LSF invokes the RESUME action when:
◆ The user or LSF administrator issues a bresume command to the job
◆ Load conditions on the execution host satisfy all of:
❖ The resume conditions of the queue, as specified by the RESUME_COND
parameter in
lsb.queues
❖ The scheduling thresholds of the queue and the execution host
◆ A closed run window of the queue opens again
◆ A preempted job finishes
TERMINATE action
Terminate a job. This usually causes the job change to EXIT status. The default
action is to send SIGINT first, then send SIGTERM 10 seconds after SIGINT, then
send SIGKILL 10 seconds after SIGTERM. The delay between signals allows user
programs to catch the signals and clean up before the job terminates.
To override the 10 second interval, use the parameter
JOB_TERMINATE_INTERVAL in the
lsb.params file. See the Platform LSF
Configuration Reference for information about the
lsb.params file.
LSF invokes the TERMINATE action when:
◆ The user or LSF administrator issues a bkill or brequeue command to the job
◆ The TERMINATE_WHEN parameter in the queue definition (lsb.queues)
causes a SUSPEND action to be redirected to TERMINATE
◆ The job reaches its CPULIMIT, MEMLIMIT, RUNLIMIT or PROCESSLIMIT
If the execution of an action is in progress, no further actions are initiated unless it
is the TERMINATE action. A TERMINATE action is issued for all job states except
PEND.