Platform LSF Administration Guide Version 6.2

Cluster Concepts
Administering Platform LSF
56
Hosts
Host
An individual computer in the cluster.
Each host may have more than 1 processor. Multiprocessor hosts are used to run parallel
jobs. A multiprocessor host with a single process queue is considered a single machine,
while a box full of processors that each have their own process queue is treated as a
group of separate machines.
Commands
◆ lsload—View load on hosts
◆ lshosts—View configuration information about hosts in the cluster including
number of CPUS, model, type, and whether the host is a client or server
◆ bhosts—View batch server hosts in the cluster
The names of your hosts should be unique. They should not be the same as the
cluster name or any queue defined for the cluster.
Submission host
The host where jobs are submitted to the cluster.
Jobs are submitted using the
bsub command or from an application that uses the LSF
API.
Client hosts and server hosts can act as submission hosts.
Commands
◆ bsub—Submit a job
◆ bjobs—View jobs that are submitted
Execution host
The host where a job runs. Can be the same as the submission host. All execution hosts
are server hosts.
Commands
◆ bjobs—View where a job runs
Server host
Hosts that are capable of submitting and executing jobs. A server host runs sbatchd
to execute server requests and apply local policies.
Commands
◆ lshosts—View hosts that are servers (server=Yes)
Configuration
◆ Server hosts are defined in the lsf.cluster.cluster_name file by setting the
value of
server to 1
Client host
Hosts that are only capable of submitting jobs to the cluster. Client hosts run LSF
commands and act only as submission hosts. Client hosts do not execute jobs or run
LSF daemons.
Commands
◆ lshosts—View hosts that are clients (server=No)
Configuration
◆ Client hosts are defined in the lsf.cluster.cluster_name file by setting the
value of
server to 0