LSF Version 7.3 - Platform LSF Configuration Reference

The action taken when a job exceeds its SWAPLIMIT or PROCESSLIMIT is to send SIGQUIT,
SIGINT, SIGTERM, and SIGKILL in sequence. For CPULIMIT, SIGXCPU is sent before
SIGINT, SIGTERM, and SIGKILL.
Default
Unlimited
TERMINATE_WHEN
Syntax
TERMINATE_WHEN=[LOAD] [PREEMPT] [WINDOW]
Description
Configures the queue to invoke the TERMINATE action instead of the SUSPEND action in
the specified circumstance.
•
LOAD — kills jobs when the load exceeds the suspending thresholds.
•
PREEMPT — kills jobs that are being preempted.
•
WINDOW — kills jobs if the run window closes.
If the TERMINATE_WHEN job control action is applied to a chunk job, sbatchd kills the
chunk job element that is running and puts the rest of the waiting elements into pending state
to be rescheduled later.
Example
Set TERMINATE_WHEN to WINDOW to define a night queue that kills jobs if the run
window closes:
Begin Queue
NAME = night
RUN_WINDOW = 20:00-08:00
TERMINATE_WHEN = WINDOW
JOB_CONTROLS = TERMINATE[kill -KILL $LS_JOBPGIDS; mail - s "job $LSB_JOBID
killed by queue run window" $USER < /dev/null]
End Queue
THREADLIMIT
Syntax
THREADLIMIT=[default_limit] maximum_limit
Description
Limits the number of concurrent threads that can be part of a job. Exceeding the limit causes
the job to terminate. The system sends the following signals in sequence to all processes belongs
to the job: SIGINT, SIGTERM, and SIGKILL.
By default, if a default thread limit is specified, jobs submitted to the queue without a job-level
thread limit are killed when the default thread limit is reached.
If you specify only one limit, it is the maximum, or hard, thread limit. If you specify two limits,
the first one is the default, or soft, thread limit, and the second one is the maximum thread
limit.
lsb.queues
Platform LSF Configuration Reference 321