LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 465
Job Priorities
USERS: all
HOSTS: all
REQUEUE_EXIT_VALUES: 10
Feature interactions
Fairshare The default user-based fairshare can be a factor in APS calculation by adding the FS
factor to APS_PRIORITY in the queue.
◆ APS cannot be used together with DISPATCH_ORDER=QUEUE.
◆ APS cannot be used together with cross-queue fairshare
(FAIRSHARE_QUEUES). The QUEUE_GROUP parameter replaces
FAIRSHARE_QUEUES, which is obsolete in LSF 7.0.
◆ APS cannot be used together with queue-level fairshare or host-partition
fairshare.
FCFS APS overrides the job sort result of FCFS.
SLA scheduling APS cannot be used together with SLA scheduling.
Job requeue All requeued jobs are treated as newly submitted jobs for APS calculation. The job
priority, system, and ADMIN APS factors are reset on requeue.
Rerun jobs Rerun jobs are not treated the same as requeued jobs. A job typically reruns because
the host failed, not through some user action (like job requeue), so the job priority
is not reset for rerun jobs.
Job migration Suspended (bstop) jobs and migrated jobs (bmig) are always scheduled before
pending jobs. For migrated jobs, LSF keeps the existing job priority information.
If LSB_REQUEUE_TO_BOTTOM and LSB_MIG2PEND are configured in
lsf.conf, the migrated jobs keep their APS information. When
LSB_REQUEUE_TO_BOTTOM and LSB_MIG2PEND are configured, the
migrated jobs need to compete with other pending jobs based on the APS value. If
you want to reset the APS value, the you should use
brequeue, not bmig.
Resource
reservation
The resource reservation is based on queue policies. The APS value does not affect
current resource reservation policy.
Preemption The preemption is based on queue policies. The APS value does not affect the
current preemption policy.
Chunk jobs The first chunk job to be dispatched is picked based on the APS priority. Other jobs
in the chunk is picked based on the APS priority and the default chunk job
scheduling policies.
The following job properties must be the same for all chunk jobs:
◆ Submitting user
◆ Resource requirements
◆ Host requirements
◆ Queue or application profile