Submit and modify jobs using advance reservations


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 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

Before you begin

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.