LSF Version 7.3 - Platform LSF Configuration Reference

The LIM on the first host listed becomes the master LIM if this host is up; otherwise, that on
the second becomes the master if its host is up, and so on. Also, to avoid the delays involved
in switching masters if the first machine goes down, the master should be on a reliable machine.
It is desirable to arrange the list such that the first few hosts in the list are always in the same
subnet. This avoids a situation where the second host takes over as master when there are
communication problems between subnets.
Configuration information is of two types:
•
Some fields in a host entry simply describe the machine and its configuration.
•
Other fields set thresholds for various resources.
Example Host section
This example Host section contains descriptive and threshold information for three hosts:
Begin Host
HOSTNAME model type server r1m pg tmp RESOURCES RUNWINDOW
hostA SparcIPC Sparc 1 3.5 15 0 (sunos frame) ()
hostD Sparc10 Sparc 1 3.5 15 0 (sunos) (5:18:30-1:8:30)
hostD ! ! 1 2.0 10 0 () ()
hostE ! ! 1 2.0 10 0 (linux !bigmem) ()
End Host
Descriptive fields
The following fields are required in the Host section:
•
HOSTNAME
•
RESOURCES
•
type
•
model
The following fields are optional:
•
server
•
nd
•
RUNWINDOW
•
REXPRI
HOSTNAME
Description
Official name of the host as returned by hostname(1)
The name must be listed in lsf.shared as belonging to this cluster.
model
Description
Host model
The name must be defined in the HostModel section of lsf.shared. This determines the
CPU speed scaling factor applied in load and placement calculations.
Optionally, the ! keyword for the model or type column, indicates that the host model or type
is to be automatically detected by the LIM running on the host.
lsf.cluster
Platform LSF Configuration Reference 381