Administering Platform LSF - SAS

Using Advance Reservation
Modifying jobs
(bmod -U)
Changing job
termination time
(bmod -t)
IMPORTANT
Job resource
usage limits
Preemption and
fairshare
Administrators can use the -U option of bmod to change a job to another
reservation ID. For example:
%bmod -U user1#0 1234
To cancel the reservation, use the -Un option of bmod. For example:
%bmod -Un 1234
Before the reservation window closes, administrators can use the -t option of
bmod to change the termination time of a running job that is using the
reservation. This prevents the job from being killed when the reservation
expires; it does not extend the actual reservation window. For example:
%bmod -t 15:0 1234
You must set LSB_MOD_ALL_JOBS=Y in lsf.conf to use bmod -t for
advance reservations.
bmod -t will not change the termination time of a pending job.
A job using a reservation is subject to all job resource usage limits. If a limit is
reached on a particular host in a reservation, jobs using that reservation cannot
start on that host.
Higher priority jobs can only preempt other jobs that use the same reservation.
In fairshare, a lower priority job can run as long as no other higher priority
share holders can access the same reservation as the lower priority job.
Forcing a job to run before a reservation is active
LSF administrators can use brun to force jobs to run before the reservation is
active, but the job must finish running before the time window of the
reservation expires.
For example, if the administrator forces a job with a reservation to run one
hour before the reservation is active, and the reservation period is 3 hours, a
4 hour run limit takes effect.
Advance reservations across clusters
You can create and use advance reservation for the MultiCluster job forwarding
model. To enable this feature, you must upgrade all clusters to LSF Version 6.0
or later.
See the Using Platform LSF MultiCluster for more information.
472
Administering Platform LSF