Platform LSF Reference Version 6.2

lsb.queues
Platform LSF Reference
413
JOB_WARNING_ACTION
Syntax JOB_WARNING_ACTION=signal
Description
Specifies the job action to be taken before a job control action occurs. For example, 2
minutes before the job reaches run time limit or termination deadline, or the queue's run
window is closed, an URG signal is sent to the job.
A job warning action must be specified with a job action warning time in order for job
warning to take effect.
If JOB_WARNING_ACTION is specified, LSF sends the warning action to the job
before the actual control action is taken. This allows the job time to save its result before
being terminated by the job control action.
You can specify actions similar to the JOB_CONTROLS queue level parameter: send a
signal, invoke a command, or checkpoint the job.
The warning action specified by the
bsub -wa option overrides
JOB_WARNING_ACTION in the queue. JOB_WARNING_ACTION is used as the
default when no command line option is specified.
Example
JOB_WARNING_ACTION=URG
Default
Undefined
load_index
Syntax
load_index=loadSched[/loadStop]
Specify
io, it, ls, mem, pg, r15s, r1m, r15m, swp, tmp, ut, or a non-shared custom
external load index. Specify multiple lines to configure thresholds for multiple load
indices.
Specify
io, it, ls, mem, pg, r15s, r1m, r15m, swp, tmp, ut, or a non-shared custom
external load index as a column. Specify multiple columns to configure thresholds for
multiple load indices.
Description
Scheduling and suspending thresholds for the specified dynamic load index.
The
loadSched condition must be satisfied before a job is dispatched to the host. If a
RESUME_COND is not specified, the
loadSched condition must also be satisfied
before a suspended job can be resumed.
If the
loadStop condition is satisfied, a job on the host will be suspended.
The
loadSched and loadStop thresholds permit the specification of conditions
using simple AND/OR logic. Any load index that does not have a configured threshold
has no effect on job scheduling.
LSF will not suspend a job if the job is the only batch job running on the host and the
machine is interactively idle (
it>0).
The
r15s, r1m, and r15m CPU run queue length conditions are compared to the
effective queue length as reported by
lsload -E, which is normalized for
multiprocessor hosts. Thresholds for these parameters should be set at appropriate
levels for single processor hosts.