Platform LSF Administration Guide Version 6.2

Chapter 20
Advance Reservation
Administering Platform LSF
369
At 15:50, both Job 122 in reservation user#17 and Job 245 in reservation user#18
are suspended. At this point, the existing scheduling policies determine which job runs;
in this example, Job 122 in reservation
user#17 runs.
IMPORTANT
bmod -t will not change the termination time of a pending job.
Job resource
usage limits
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.
Preemption and
fairshare
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.2 or later.
See the Using Platform LSF MultiCluster for more information.
Viewing historical accounting information for advance reservations
bacct -U
Use the -U option of the bacct command to display accounting information about
advance reservations.
bacct -U displays information similar to the brsvs command:
◆ The reservation ID specified on the -U option.
◆ The type of reservation: user or system
◆ The user names of users who used the brsvadd command to create the advance
reservations
◆ The user names of the users who can use the advance reservations (with bsub -U)
◆ Number of CPUs reserved
◆ List of hosts for which processors are reserved
◆ Time window for the reservation.
❖ A one-time reservation displays fields separated by slashes
(
month/day/hour/minute). For example:
11/12/14/0-11/12/18/0
❖ A recurring reservation displays fields separated by colons
(
day:hour:minute). For example:
5:18:0 5:20:0