Command Reference Guide

Platform LSF Command Reference 73
◆ The host on which a rerunnable job is running is unavailable and the job has
been requeued by LSF with a new job ID, as if the job were submitted as a new
job.
◆ After the execution host becomes available, LSF tries to kill the ZOMBI job.
Upon successful termination of the ZOMBI job, the job’s status is changed to
EXIT.
With MultiCluster, when a job running on a remote execution cluster becomes
a ZOMBI job, the execution cluster treats the job the same way as local ZOMBI
jobs. In addition, it notifies the submission cluster that the job is in ZOMBI
state and the submission cluster requeues the job.
RUNTIME Estimated run time for the job, specified by bsub -We or bmod -We.
RESOURCE USAGE For the MultiCluster job forwarding model, this information is not shown if
MultiCluster resource usage updating is disabled.
The values for the current usage of a job include:
CPU time
Cumulative total CPU time in seconds of all processes in a job.
IDLE_FACTOR
Job idle information (CPU time/runtime) if JOB_IDLE is configured in the queue,
and the job has triggered an idle exception.
MEM
Total resident memory usage of all processes in a job. By default, memory usage is
shown in MB. Use LSF_UNIT_FOR_LIMITS in
lsf.conf to specify a larger unit
for display (MB, GB, TB, PB, or EB).
SWAP
Total virtual memory usage of all processes in a job. By default, swap space is shown
in MB. Use LSF_UNIT_FOR_LIMITS in
lsf.conf to specify a larger unit for
display (MB, GB, TB, PB, or EB).
NTHREAD
Number of currently active threads of a job.
PGID
Currently active process group ID in a job.
PIDs
Currently active processes in a job.
RESOURCE LIMITS The hard resource usage limits that are imposed on the jobs in the queue (see
getrlimit(2) and lsb.queues(5)). These limits are imposed on a per-job and a
per-process basis.
The possible per-job resource usage limits are:
◆ CPULIMIT
◆ PROCLIMIT
◆ MEMLIMIT