Platform LSF Reference Version 6.2

bsub
Platform LSF Reference
171
- RUN, DONE, or EXIT
- PEND or PSUSP, and the job has a pre-execution command (
bsub -E) that
is running.
-W [hour:]minute[/host_name | /host_model]
Sets the run time limit of the batch job. If a UNIX job runs longer than the specified
run limit, the job is sent a SIGUSR2 signal, and is killed if it does not terminate within
ten minutes. If a Windows job runs longer than the specified run limit, it is killed
immediately. (For a detailed description of how these jobs are killed, see
bkill.) In the
queue definition, a TERMINATE action can be configured to override the
bkill
default action (see the JOB_CONTROLS parameter in
lsb.queues(5)).
The run limit is in the form of [hour
:]minute. The minutes can be specified as a number
greater than 59. For example, three and a half hours can either be specified as 3:30, or
210.
The run limit you specify is the normalized run time. This is done so that the job does
approximately the same amount of processing, even if it is sent to host with a faster or
slower CPU. Whenever a normalized run time is given, the actual time on the execution
host is the specified time multiplied by the CPU factor of the normalization host then
divided by the CPU factor of the execution host.
If ABS_RUNLIMIT=Y is defined in
lsb.params, the run time limit is not normalized
by the host CPU factor. Absolute wall-clock run time is used for all jobs submitted with
a run limit.
Optionally, you can supply a host name or a host model name defined in LSF. You must
insert ‘
/’ between the run limit and the host name or model name. (See lsinfo(1) to
get host model information.)
If no host or host model is given, LSF uses the default run time normalization host
defined at the queue level (DEFAULT_HOST_SPEC in
lsb.queues) if it has been
configured; otherwise, LSF uses the default CPU time normalization host defined at the
cluster level (DEFAULT_HOST_SPEC in
lsb.params) if it has been configured;
otherwise, LSF uses the submission host.
For MultiCluster jobs, if no other CPU time normalization host is defined and
information about the submission host is not available, LSF uses the host with the
largest CPU factor (the fastest host in the cluster).
If the job also has termination time specified through the
bsub -t option, LSF
determines whether the job can actually run for the specified length of time allowed by
the run limit before the termination time. If not, then the job will be aborted.
If the IGNORE_DEADLINE parameter is set in
lsb.queues(5), this behavior is
overridden and the run limit is ignored.
Jobs submitted to a chunk job queue are not chunked if the run limit is greater than 30
minutes.
-wa '[signal | command | CHKPNT]'
Specifies the job action to be taken before a job control action occurs.
A job warning action must be specified with a job action warning time in order for job
warning to take effect.