LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 663
Tuning the Cluster
◆ In sites where each host in the cluster cannot share a common configuration
directory or exact replica.
In this section ◆ Default LIM behavior on page 663
◆ Changing Default LIM Behavior to Improve Performance on page 662
◆ Reconfiguration and LSF_MASTER_LIST on page 663
◆ How LSF works with LSF_MASTER_LIST on page 664
◆ Considerations on page 665
Default LIM behavior
By default, each LIM running in an LSF cluster must read the configuration files
lsf.shared and lsf.cluster.cluster_name to obtain information about resource
definitions, host types, host thresholds, etc. This includes master and slave LIMs.
This requires that each host in the cluster share a common configuration directory
or an exact replica of the directory.
Change default LIM behavior
The parameter LSF_MASTER_LIST in lsf.conf allows you to identify for the LSF
system which hosts can become masters. Hosts not listed in LSF_MASTER_LIST
will be considered as slave-only hosts and will never be considered to become
master.
Set LSF_MASTER_LIST (lsf.conf)
1 Edit lsf.conf and set the parameter LSF_MASTER_LIST to indicate hosts
that are candidates to become the master host. For example:
LSF_MASTER_LIST="hostA hostB hostC"
The order in which you specify hosts in LSF_MASTER_LIST is the preferred
order for selecting hosts to become the master LIM.
2 Save your changes.
3 Reconfigure the cluster
lsadmin reconfig
badmin mbdrestart.
Reconfiguration and LSF_MASTER_LIST
If you change LSF_MASTER_LIST
Whenever you change the parameter LSF_MASTER_LIST, reconfigure the cluster
with
lsadmin reconfig and badmin mbdrestart.
If you change lsf.cluster.cluster_name or lsf.shared
If you make changes that do not affect load report messages such as adding or
removing slave-only hosts, you only need to restart the LIMs on all master
candidates with the command
lsadmin limrestart and the specific host names.
For example:
lsadmin limrestart hostA hostB hostC