LSF Version 7.3 - Administering Platform LSF
Using Advance Reservation
440 Administering Platform LSF
by jobs referencing user2#0, hostA is no longer available to other jobs using
reservation
user2#0. Any single user or user group can have a maximum of 100
reservation IDs.
Jobs referencing the reservation are killed when the reservation expires.
Modify job reservation ID
Prerequisites: You must be an administrator to perform this task.
1 Use the -U option of bmod to change a job to another reservation ID.
For example:
bmod -U user1#0 1234
2 To cancel the reservation, use the -Un option of bmod.
For example:
bmod -Un 1234
Use bmod -Un to detach a running job from an inactive open reservation. Once
detached, the job is scheduled like a normal job.
Job resource usage limits and job chunking
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.
An advance reservation job is dispatched to its reservation even if the run limit or
estimated run time of the job exceeds the remaining active time of the reservation.
For example, if a job has a runlimit of 1 hour, and a reservation has a remaining
active time of 1 minute, the job is still dispatched to the reservation. If the
reservation is closed, the job is terminated when the reservation expires.
Similarly, when using chunk job scheduling, advance reservation jobs are chunked
together as usual when dispatched to a host of the reservation without regard to the
expiry time of the reservation. This is true even when the jobs are given a run limit
or estimated run time. If the reservation is closed, the jobs in WAIT state are
terminated when the reservation expires.
Advance reservation preemption
Advance reservation preemption allows advance reservation jobs to use the slots
reserved by the reservation. Slots occupied by non-advance jobs may be preempted
when the reservation becomes active.
Without modification with
brsvmod, advance reservation preemption is triggered
at most once per reservation period (in the case of a non-recurring reservation,
there is only one period) whenever both of the following conditions are met:
◆ The reservation is active
◆ At least one job associated with the advance reservation is pending or
suspended