LSF Version 7.3 - Administering Platform LSF

About Resource Preemption
328 Administering Platform LSF
About Resource Preemption
Preemptive Scheduling and Resource Preemption
Resource preemption is a special type of preemptive scheduling. It is similar to job
slot preemption.
Job Slot Preemption and Resource Preemption
If you enable preemptive scheduling, job slot preemption is always enabled.
Resource preemption is optional. With resource preemption, you can configure
preemptive scheduling based on other resources in addition to job slots.
Types of Resource Preemption
License Preemption If you have configured a custom resource to manage software application licenses
that are shared throughout the cluster (Network Floating Licenses), you can use
preemptive scheduling to make these licenses more available to high-priority
queues.
The license resource can be either static (network floating licenses managed within
LSF) or dynamic and decreasing (network floating licenses outside of LSF control
and measured with an ELIM).
Other Resources Resource preemption works for any custom shared numeric resource (except
increasing dynamic resources) so its use is not restricted to managing licenses. To
preempt on a host-based resource, such as memory, you could configure a custom
resource "shared" on only one host.
Multiple Resource Preemption
If multiple resources are required, LSF can preempt multiple jobs, until sufficient
resources are available. For example, one or more jobs might be preempted for a job
that needs:
◆ Multiple job slots
◆ Multiple licenses for one software application
◆ Multiple resources, such as a job slot, a license, and memory
◆ More of a resource than can be obtained by preempting just one job
Using Resource Preemption
To allow your job to participate in resource preemption, you must use resource
reservation to reserve the preemption resource (the cluster might be configured so
that this occurs automatically). For dynamic resources, you must specify a duration
also.
Resource reservation is part of resource requirement, which can be specified at the
job level or at the queue level or application level.
You can use a task file to associate specific resource requirements with specific
applications.