LSF Version 7.3 - Platform LSF Configuration Reference

1.
In the order phase, the scheduler applies policies such as FCFS, Fairshare and Host-
partition and consider job priorities within user groups and share groups. By default,
job priority within a pool of jobs from the same user is based on how long the job has
been pending.
2.
For resource intensive jobs (jobs requiring a lot of CPUs or a large amount of memory),
resource reservation is performed so that these jobs are not starved.
3.
When all the currently available resources are allocated, jobs go on to post-processing.
4.
Post-processing — the scheduler prepares jobs from the order/allocation phase for
dispatch and applies preemption or backfill policies to obtain resources for the jobs that
have completed pre-processing or match/limit phases, but did not have resources available
to enter the next scheduling phase.
Each scheduler plugin module invokes one or more scheduler phase. The processing for a give
phase can be disabled or skipped if:
The plugin module does not need to do any processing for that phase or the processing has
already been done by a previous plugin module in the list.
The scheduler will not invoke phases marked by SCH_DISABLE_PHASES when scheduling
jobs.
None of the plugins provided by LSF should require phases to be disabled, but your own
custom plugin modules using the scheduler SDK may need to disable one or more scheduler
phases.
Example
In the following configuration, the schmod_custom plugin module disables the order
allocation (3) and post-processing (4) phases:
NAME SCH_DISABLE_PHASES
schmod_default ()
schmod_custom (3,4)
Default
Undefined
lsb.modules
234 Platform LSF Configuration Reference