LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 439
Advance Reservation
Reservation Status: Inactive
Reservation disabled for these dates:
Fri Feb 15 2008
Wed Feb 20 2008 - Mon Feb 25 2008
Next Active Period:
Sat Feb 16 10:00:00 2008 - Sat Feb 16 12:00:00 2008
Creator: user1
Reservation Type: CLOSED
RSVID TYPE USER NCPUS RSV_HOSTS TIME_WINDOW
user1#6 user user1 0/1 hostA:0/1 10:00-13:00 *
Reservation Status: Active
Creator: user1
Reservation Type: CLOSED
Show reservation ID
1 Use bjobs -l to show the reservation ID used by a job:
bjobs -l
Job <1152>, User <user1>, Project <default>, Status <PEND>, Queue
<normal>, Reservation <user1#0>, Command <myjob>
Mon Nov 12 5:13:21: Submitted from host <hostB>, CWD
</home/user1/jobs>;
Submit and modify jobs using advance reservations
1 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).
If you later delete the advance reservation while it is still active, any pending
jobs still keep the
"type==any" attribute.
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