Administering Platform LSF - SAS

Chapter 35
Advance Reservation
2:50 0 0 0 1024 0 0 0
3:0 0 0 0 0 0 0 0
3:10 0 0 0 0 0 0 0
3:20 0 0 0 0 0 0 0
...
23:30 0 0 0 0 0 0 0
23:40 0 0 0 0 0 0 0
23:50 0 0 0 0 0 0 0
bjobs command
Use bjobs -l to show the reservation ID used by a job:
% bjobs -l
Job , User , Project , Status ,
Queue , Reservation , Command
Mon Nov 12 5:13:21: Submitted from host , CWD
;
Submitting and modifying jobs using advance reservations
Submitting and
running jobs
(bsub -U)
Use the -U option of bsub to submit jobs with a reservation ID. For example:
%bsub -U user1#0 myjob
The job can only use hosts reserved by the reservation user1#0. By default,
LSF selects only hosts in the reservation. Use the -m option to specify particular
hosts within the list of hosts reserved by the reservation; you can only select
from hosts that were included in the original reservation.
If you do not specify hosts (bsub -m) or resource requirements (bsub -R), the
default resource requirement is to select hosts that are of any host type (LSF
assumes "type==any" instead of "type==local" as the default select string.)
A job can only use one reservation. There is no restriction on the number of
jobs that can be submitted to a reservation; however, the number of slots
available on the hosts in the reservation may run out. For example, reservation
user2#0 reserves 1024 slots on hostA. When all 1024 slots on hostA are used
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. LSF
administrators can prevent running jobs from being killed when the reservation
expires by changing the termination time of the job using the reservation
(bmod -t) before the reservation window closes.
Administering Platform LSF 471