Platform LSF Administration Guide Version 6.2
User-Assigned Job Priority
Administering Platform LSF
382
User-Assigned Job Priority
User-assigned job priority provides controls that allow users to order their jobs in a
queue. Job order is the first consideration to determine job eligibility for dispatch. Jobs
are still subject to all scheduling policies regardless of job priority. Jobs with the same
priority are ordered first come first served.
The job owner can change the priority of their own jobs. LSF and queue administrators
can change the priority of all jobs in a queue.
User-assigned job priority is enabled for all queues in your cluster, and can be configured
with automatic job priority escalation to automatically increase the priority of jobs that
have been pending for a specified period of time.
Considerations
The btop and bbot commands move jobs relative to other jobs of the same priority.
These commands do not change job priority.
In this section
◆
“Configuring job priority” on page 382
◆
“Specifying job priority” on page 382
◆
“Viewing job priority information” on page 383
Configuring job priority
To configure user-assigned job priority edit lsb.params and define
MAX_USER_PRIORITY. This configuration applies to all queues in your cluster.
Use
bparams -l to display the value of MAX_USER_PRIORITY.
Syntax
MAX_USER_PRIORITY=
max_priority
Where:
max_priority
Specifies the maximum priority a user can assign to a job. Valid values are positive
integers. Larger values represent higher priority; 1 is the lowest.
LSF and queue administrators can assign priority beyond max_priority.
Example
MAX_USER_PRIORITY=100
Specifies that 100 is the maximum job priority that can be specified by a user.
Specifying job priority
Job priority is specified at submission using bsub and modified after submission using
bmod. Jobs submitted without a priority are assigned the default priority of
MAX_USER_PRIORITY/2.
Syntax
bsub -sp
priority
bmod [-sp
priority
| -spn]
job_ID
Where:
◆
-sp priority
Specifies the job priority. Valid values for priority are any integers between 1 and
MAX_USER_PRIORITY (displayed by
bparams -l). Incorrect job priorities are
rejected.