LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 23
About Platform LSF
Primary LSF
administrator
The first cluster administrator specified during installation and first administrator
listed in
lsf.cluster.cluster_name. The primary LSF administrator account owns
the configuration and log files. The primary LSF administrator has permission to
perform clusterwide operations, change configuration files, reconfigure the cluster,
and control jobs submitted by all users.
Cluster
administrator
May be specified during LSF installation or configured after installation. Cluster
administrators can perform administrative operations on all jobs and queues in the
cluster. Cluster administrators have the same cluster-wide operational privileges as
the primary LSF administrator except that they do not necessarily have permission
to change LSF configuration files.
For example, a cluster administrator can create an LSF host group, submit a job to
any queue, or terminate another user’s job.
Queue
administrator
An LSF administrator user account that has administrative permissions limited to
a specified queue. For example, an LSF queue administrator can perform
administrative operations on the specified queue, or on jobs running in the
specified queue, but cannot change LSF configuration or operate on LSF daemons.
Resources
Resource usage The LSF system uses built-in and configured resources to track resource availability
and usage. Jobs are scheduled according to the resources available on individual
hosts.
Jobs submitted through the LSF system will have the resources they use monitored
while they are running. This information is used to enforce resource limits and load
thresholds as well as fairshare scheduling.
LSF collects information such as:
◆ Total CPU time consumed by all processes in the job
◆ Total resident memory usage in KB of all currently running processes in a job
◆ Total virtual memory usage in KB of all currently running processes in a job
◆ Currently active process group ID in a job
◆ Currently active processes in a job
On UNIX, job-level resource usage is collected through PIM.
Commands:
◆ lsinfo—View the resources available in your cluster
◆ bjobs -l—View current resource usage of a job
Configuration:
◆ SBD_SLEEP_TIME in lsb.params—Configures how often resource usage
information is sampled by PIM, collected by
sbatchd, and sent to mbatchd
Load indices Load indices measure the availability of dynamic, non-shared resources on hosts in
the cluster. Load indices built into the LIM are updated at fixed time intervals.
Commands:
◆ lsload -l—View all load indices