Platform LSF Administration Guide Version 6.2

Upgrade and Compatibility Notes
Administering Platform LSF
42
from hostD1 to hostD100, hostD102, all hosts from hostD201 to
hostD300, and hostD320):
... (hostD[1-100,102,201-300,320])
Restrictions
❖ You cannot use more than one set of square brackets in a single host group
definition.
The following example is not correct:
... (hostA[1-10]B[1-20] hostC[101-120])
The following example is correct:
... (hostA[1-20] hostC[101-120])
❖ You cannot define subgroups that contain wildcards and special characters. The
following definition for
groupB is not correct because groupA defines hosts
with a wildcard:
Begin HostGroup
GROUP_NAME GROUP_MEMBER
groupA (hostA*)
groupB (groupA)
End HostGroup
lsb.params
◆ MAX_INFO_DIRS=num_subdirs
Where num_subdirs specifies the number of subdirectories that you want to create
under the
LSF_SHAREDIR/cluster_name/logdir/info directory. Valid
values are positive integers between 1 and 1024. The default value is 0.
If your cluster has a lot of jobs resulting in a large info directory, you can tune your
cluster by enabling LSF to create subdirectories in the info directory. Use
MAX_INFO_DIRS in
lsb.params to create the subdirectories and enable
mbatchd to distribute the job files evenly throughout the subdirectories.
For example:
MAX_INFO_DIRS=10
mbatchd creates ten subdirectories from
LSB_SHAREDIR/cluster_name/logdir/info/0
to
LSB_SHAREDIR/cluster_name/logdir/info/9
Run badmin reconfig to create and use the subdirectories. If you enabled
duplicate event logging, run
badmin mbdrestart instead to restart mbatchd.
If you specify MAX_INFO_DIRS after upgrading and decide to roll back the
upgrade, pending jobs cannot be dispatched after downgrading to the previous
release. You must kill the pending jobs and resubmit them.
lsb.queues
◆ USERS=all [~user_name ...] [~user_group ...] |
[user_name ...] [user_group ... [~user_group ...]]
Use the not operator (
~) to exclude users from the the all specification or from
user groups. This is useful if you have a large number of users but only want to
exclude a few users or groups from the queue definition.