SCHEDULING PARAMETERS: |
|
|
|
|
|
|
|
| |||
| r15s r1m r15m | ut | pg | io | ls | it tmp swp mem | |||||
loadSched | - | - | - | - | - | - | - | - | - | - | - |
loadStop | - | - | - | - | - | - | - | - | - | - | - |
EXTERNAL MESSAGES: |
|
|
|
|
|
|
|
|
|
MSG_ID | FROM | POST_TIME | MESSAGE | ATTACHMENT |
0 | - | - | - | - |
1 | lsfadmin | date and time | SLURM[nodes=2] | N |
Example 2. Four cores on Two Specific Nodes
This example submits a job that requests four cores on two specific nodes, on an XC system that has three compute nodes.
Submit the job:
$ bsub
<<Waiting for dispatch ...>> <<Starting on lsfhost.localdomain>> n14
n14
n16
n16
View the job:
$ bjobs -l 9
Job <9>, User <smith>, Project <default>, Status <DONE>,
Queue <normal>, Interactive mode, Extsched <SLURM[nodelist=n[14,16]]>, Command <srun hostname>
date and time stamp: Submitted from host <lsfhost.localdomain>, CWD <$HOME>, 4 Processors Requested;
date and time stamp: Started on 4 Hosts/Processors <4*lsfhost.localdomain>;
date and time stamp: slurm_id=24;ncpus=4;<SLURM[nodelist=n[14,16]]>;
date and time stamp: Done successfully. The CPU time used is 0.0 seconds.
SCHEDULING PARAMETERS: |
|
|
|
|
|
|
|
| |||
| r15s r1m r15m | ut | pg | io | ls | it tmp swp mem | |||||
loadSched | - | - | - | - | - | - | - | - | - | - | - |
loadStop | - | - | - | - | - | - | - | - | - | - | - |
EXTERNAL | MESSAGES: |
|
|
|
MSG_ID | FROM | POST_TIME | MESSAGE | ATTACHMENT |
0 | - | - | - | - |
1 | lsfadmin | date and time | SLURM[nodelist=n[14,16]] | N |
Launching a Parallel Interactive Shell Through LSF-HPC
This section provides an example that shows how to launch a parallel interactive shell through
Examine the LSF execution host information:
$ bhosts |
|
|
|
|
|
|
|
|
HOST_NAME | STATUS | JL/U | MAX | NJOBS RUN SSUSP | USUSP | RSV | ||
lsfhost.localdomain | ok | - | 12 | 0 | 0 | 0 | 0 | 0 |
Submit the job: 101