4 how lsf and slurm launch and manage a job, Section 7.1.4 – HP XC System 2.x Software User Manual
Page 88
queue contains the job starter script, but the
unscripted
queue does not have the job
starter script configured.
Example 7-1: Comparison of Queues and the Configuration of the Job Starter
Script
$ bqueues -l normal | grep JOB_STARTER
JOB_STARTER:
/opt/hptc/lsf/bin/job_starter.sh
$ bqueues -l unscripted | grep JOB_STARTER
JOB_STARTER:
$ bsub -Is hostname
Job <66> is submitted to the default queue
<
<
n10
$ bsub -Is -q unscripted hostname
Job <67> is submitted to the default queue
<
<
n20
•
Use the
bjobs -l
and
bhist -l
LSF commands to see the components of the actual
SLURM allocation command.
•
Use the
bkill
command to kill jobs.
•
Use the
bjobs
command to monitor job status in LSF.
•
Use the
bqueues
command to list the configured job queues in LSF.
7.1.4 How LSF and SLURM Launch and Manage a Job
This section describes what happens in the HP XC system when a job is submitted to LSF.
Figure 7-1 illustrates this process. Use the numbered steps in the text and depicted in the
illustration as an aid to understanding the process.
Consider the HP XC system configuration shown in Figure 7-1, in which
lsfhost.localdomain
is the LSF execution host, node
n16
is the login node, and nodes
n[1-10]
are compute nodes in the
lsf
partition. All nodes contain two processors, providing
20 processors for use by LSF jobs.
7-4
Using LSF