
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 <normal>.
<<Waiting for dispatch...>>
<<Starting on lsfhost.localdomain>>
n10
$ bsub -Is -q unscripted hostname
Job <67> is submitted to the default queue <unscripted>.
<<Waiting for dispatch...>>
<<Starting on lsfhost.localdomain>>
n20
•Usethebjobs -l and bhist -l LSF commands to see the components of the actual
SLURM allocation command.
•Usethebkill command to kill jobs.
•Usethebjobs command to monitor job status in LSF.
•Usethebqueues 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 syst em when a job is submitted to LSF.
Figure 7-1 illustrates this process. Use the num bered steps in the text and depicted in the
illustration as an aid to understanding the process.
Consider the HP XC system configuration s how n in Figure 7-1, in which
lsfhost.localdomain is the LSF execution host, node n16 is the login nod e, 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
Komentarze do niniejszej Instrukcji