Platform LSF Administration Guide Version 6.2

Chapter 4
Working with Hosts
Administering Platform LSF
105
Upon startup, slave hosts wait to receive the acknowledgement from the master LIM.
This acknowledgement indicates to the slave host that it has already been added to the
cluster. If it does not receive the acknowledgement within the time specified by
LSF_DYNAMIC_HOST_WAIT_TIME in
lsf.conf, the slave host contacts the
master LIM to add itself to the cluster.
If you did not define LSF_DYNAMIC_HOST_WAIT_TIME in lsf.conf, the slave
host will wait indefinitely for an acknowledgement from the master LIM
without contacting the master LIM to add itself to the cluster.
Local resources
for slave hosts
Use LSF_LOCAL_RESOURCES in a localized lsf.conf to define instances of local
resources residing on the slave host:
◆ For numeric resources, defined name-value pairs:
"[resourcemap value*resource_name]"
◆ For Boolean resources, the value will be the resource name in the form:
"[resource resource_name]"
When the slave host calls the master host to add itself, it also reports its local resources.
The local resources to be added must be defined in
lsf.shared.
If the same resource is already defined in
lsf.cluster.cluster_name as default or
all, it cannot be added as a local resource. The shared resource overrides the local one.
Resources must already be mapped to hosts in the ResourceMap section of
lsf.cluster.cluster_name. If the ResourceMap section does not exist, local
resources are not added.
LSF_LOCAL_RESOURCES is usually set in the slave.config file during installation.
If LSF_LOCAL_RESOURCES are already defined in a local lsf.conf on the slave host,
lsfinstall does not add resources you define in LSF_LOCAL_RESOURCES in
slave.config. You should not have duplicate LSF_LOCAL_RESOURCES entries in
lsf.conf. If local resources are defined more than once, only the last definition is valid.
lsadmin command
The lsadmin command is now able to run on a non-LSF host. Use
lsadmin limstartup to start LIM on a newly added dynamic host.
Master failover
If the master LIM dies, the next master candidate will have the same knowledge as the
master LIM about dynamically added hosts in the cluster.
mbatchd
mbatchd
gets host information from master LIM; when it detects that a host has been
added dynamically,
mbatchd automatically reconfigures itself.
After adding a batch host dynamically, you may have to wait a few moments for
mbatchd to detect the host and reconfigure. Depending on system load, mbatchd
may wait up to a maximum of 10 minutes before reconfiguring.
Host configuration in lsb.hosts and lsb.queues
For host configuration in lsb.hosts and lsb.queues to apply to dynamically added
hosts, use
default or all, as appropriate, to enable configuration to apply to all hosts
in the cluster.