6 notes about using lsf in the hp xc environment, 1 job startup and job control, 2 preemption support – HP XC System 2.x Software User Manual

Page 91: 2 determining execution host, 3 determining available system resources, 1 getting status of lsf, Section 7.3.1, Section 7.2), Section 7.3)

Advertising
background image

LSF does not support chunk jobs. If a job is submitted to chunk queue, SLURM will let
the job pend.

LSF does not support topology-aware advanced reservation scheduling.

7.1.6 Notes About Using LSF in the HP XC Environment

This section provides some additional information that should be noted about using LSF in
the HP XC Environment.

7.1.6.1 Job Startup and Job Control

When LSF starts a SLURM job, it sets

SLURM_JOBID

to associate the job with the SLURM

allocation. During job running, all LSF supported operating-system-enforced resource limits
are supported, including core limit, cputime limit, data limit, file size limit, memory limit, and
stack limit. If the user kills a job, LSF propagates signals to entire job, including the job file
running on the local node and all tasks running on remote nodes.

7.1.6.2 Preemption Support

LSF uses the SLURM "node share" feature to support preemption. When a low-priority is job
preempted, job processes are suspended on allocated nodes, and LSF places the high-priority job
on the same node. After high-priority job completes, LSF resumes suspended low-priority jobs.

7.2 Determining Execution Host

The

lsid

command displays the name of the HP XC system, and the name of the LSF

execution host, along with some general LSF information.

$ lsid

Platform LSF HPC 6.0 for SLURM, Sep 23 2004

Copyright 1992-2004 Platform Computing Corporation

My cluster name is penguin

My master name is lsfhost.localdomain

In this example,

penguin

is the HP XC system name (where is user is logged in and which

contains the compute nodes), and

lsfhost.localdomain

is the node where LSF is

installed and runs (LSF execution host).

7.3 Determining Available System Resources

For best use of system resources when launching an application, it is useful to know beforehand
what system resources are available for your use. This section describes how to obtain
information about system resources such as the number of processors available, LSF execution
host node information, and LSF system queues.

7.3.1 Getting Status of LSF

The

bhosts

command displays LSF resource usage information. This command is useful to

check the status of the system processors. The

bhosts

command provides a summary of the

jobs on the system and information about the current state of LSF. For example, it can be used
to determine if LSF is ready to start accepting batch jobs.

LSF daemons run on only one node in the HP XC system, so the

bhosts

command will

list one host, which represents all the resources of the HP XC system. The total number
of processors for that host should be equal to the total number of processors assigned to the
SLURM

lsf

partition.

By default, this command returns the host name, host status, and job state statistics.

Using LSF

7-7

Advertising