LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 325
Fairshare Scheduling
2 Configure a host partition for the host, and assign the shares appropriately.
Begin HostPartition
HPART_NAME = big_servers
HOSTS = hostH
USER_SHARES = [eng_users, 7] [acct_users, 3]
End HostPartition
Equal Share
Equal share balances resource usage equally between users.
Configure equal
share
1 To configure equal share, use the keyword default to define an equal share for
every user.
Begin HostPartition
HPART_NAME = equal_share_partition
HOSTS = all
USER_SHARES = [default, 1]
End HostPartition
Priority user and static priority fairshare
There are two ways to configure fairshare so that a more important user’s job always
overrides the job of a less important user, regardless of resource use.
◆ Priority User Fairshare: Dynamic priority is calculated as usual, but more
important and less important users are assigned a drastically different number
of shares, so that resource use has virtually no effect on the dynamic priority:
the user with the overwhelming majority of shares always goes first. However,
if two users have a similar or equal number of shares, their resource use still
determines which of them goes first. This is useful for isolating a group of
high-priority or low-priority users, while allowing other fairshare policies to
operate as usual most of the time.
◆ Static Priority Fairshare: Dynamic priority is no longer dynamic, because
resource use is ignored. The user with the most shares always goes first. This is
useful to configure multiple users in a descending order of priority.
Configure priority user fairshare
A queue is shared by key users and other users.
Priority user fairshare gives priority to important users, so their jobs override the
jobs of other users. You can still use fairshare policies to balance resources among
each group of users.
If two users compete for resources, and one of them is a priority user, the priority
user’s job always runs first.
1 Define a user group for priority users in lsb.users, naming it accordingly.
For example,
key_users.