Administering Platform LSF - SAS

Suspending Conditions
Viewing suspend reason
Resuming suspended jobs
The bjobs -lp command shows the load threshold that caused LSF to
suspend a job, together with the scheduling parameters.
The use of STOP_COND affects the suspending reasons as displayed by the
bjobs command. If STOP_COND is specified in the queue and the loadStop
thresholds are not specified, the suspending reasons for each individual load
index will not be displayed.
Jobs are suspended to prevent overloading hosts, to prevent batch jobs from
interfering with interactive use, or to allow a more urgent job to run. When the
host is no longer overloaded, suspended jobs should continue running.
When LSF automatically resumes a job, it invokes the RESUME action. The
default action for RESUME is to send the signal SIGCONT.
If there are any suspended jobs on a host, LSF checks the load levels in each
dispatch turn.
If the load levels are within the scheduling thresholds for the queue and the
host, and all the resume conditions for the queue (RESUME_COND in
lsb.queues) are satisfied, the job is resumed.
If RESUME_COND is not defined, then the loadSched thresholds are used to
control resuming of jobs: all the loadSched thresholds must be satisfied for
the job to be resumed. The loadSched thresholds are ignored if
RESUME_COND is defined.
Jobs from higher priority queues are checked first. To prevent overloading the
host again, only one job is resumed in each dispatch turn.
Specifying resume condition
Viewing resume thresholds
Use RESUME_COND in lsb.queues to specify the condition that must be
satisfied on a host if a suspended job is to be resumed.
Only the select section of the resource requirement string is considered when
resuming a job. All other sections are ignored.
The bjobs -l command displays the scheduling thresholds that control when
a job is resumed.
364
Administering Platform LSF