Platform LSF Administration Guide Version 6.2

Job Life Cycle
Administering Platform LSF
64
Job Life Cycle
1 Submit a job
You submit a job from an LSF client or server with the bsub command.
If you do not specify a queue when submitting the job, the job is submitted to the default
queue.
Jobs are held in a queue waiting to be scheduled and have the PEND state. The job is
held in a job file in the
LSF_SHAREDIR/cluster_name/logdir/info/
directory, or in one of its subdirectories if MAX_INFO_DIRS is defined in
lsb.params.
Job ID
LSF assigns each job a unique job ID when you submit the job.
Job name
You can also assign a name to the job with the -J option of bsub. Unlike the job ID,
the job name is not necessarily unique.
2 Schedule job
1 mbatchd looks at jobs in the queue and sends the jobs for scheduling to mbschd
at a preset time interval (defined by the parameter
JOB_SCHEDULING_INTERVAL in
lsb.params).
2 mbschd evaluates jobs and makes scheduling decisions based on:
❖ Job priority
❖ Scheduling policies
❖ Available resources
3 mbschd selects the best hosts where the job can run and sends its decisions back to
mbatchd.
Resource information is collected at preset time intervals by the master LIM from LIMs
on server hosts. The master LIM communicates this information to
mbatchd, which in
turn communicates it to
mbschd to support scheduling decisions.
3 Dispatch job
As soon as mbatchd receives scheduling decisions, it immediately dispatches the jobs
to hosts.
Submission Host
Queue
Master Host
1
2
3
5
Submit job (bsub)
dispatch job
Compute Host
j
o
b
r
e
p
o
r
t
(
o
u
t
p
u
t
,
e
r
r
o
r
s
,
i
n
f
o
)
Job
PEND
Job RUN
4
6
email job report