LSF Version 7.3 - Using Platform LSF HPC

LSF Components
LSF takes full advantage of the resources of LSF for resource selection and batch job
process invocation and control.
Batch job submission to LSF using the bsub command.
Master Batch Daemon (MBD) is the policy center for LSF. It maintains information
about batch jobs, hosts, users, and queues. All of this information is used in scheduling
batch jobs to hosts.
Load Information Manager is a daemon process running on each execution host. LIM
monitors the load on its host and exchanges this information with the master LIM.
For batch submission the master LIM provides this information to
mbatchd.
The master LIM resides on one execution host and collects information from the LIMs
on all other hosts in the cluster. If the master LIM becomes unavailable, another host
will automatically take over.
Reads the environment variable LSF_PJL_TYPE, and generates the appropriate
command line to invoke the PJL. The
esub programs provided in LSF_SERVERDIR
set this variable to the proper type.
Slave Batch Daemons (SBDs) are batch job execution agents residing on the execution
hosts.
sbatchd receives jobs from mbatchd in the form of a job specification and
starts RES to run the job according the specification.
sbatchd reports the batch job
status to
mbatchd whenever job state changes.
The blaunch command provides a drop-in replacement for rsh and ssh as a
transparent method for launching parallel and distributed applications within LSF.
Parallel Application Manager is the point of control for LSF. PAM is fully integrated
with LSF. PAM interfaces the user application with the LSF system.
Remote Execution Servers reside on each execution host. RES manages all remote tasks
and forwards signals, standard I/O, resources consumption data, and parallel job
information between PAM and the tasks.
Parallel Job Launcher is any executable script or binary capable of starting parallel tasks
on all hosts assigned for a parallel job (for example,
mpirun, poe, prun.)
TaskStarter is an executable responsible for starting a task on the local host and
reporting the process ID and host name to the PAM.
TaskStarter is located in
LSF_BINDIR.
The individual process of a parallel application
The host name at the top of the execution host list as determined by LSF. Starts PAM.
The most suitable hosts to execute the batch job as determined by LSF
pjl_type
LSF provides a generic esub to handle job submission requirements of your
applications. Use the
-a option of bsub to specify the application you are running
through LSF.
For example, to submit a job to LAM/MPI: