Canceling planned allocations

In an ideal world, once a planned allocation is created it will live until the job is dispatched on the resources of the planned allocation. However, in cases where LSF detects that the planned allocation has become (or may have become) invalid, the planned allocation is canceled.

When this happens, the job becomes treated like a regular job without a future allocation, but may get another future allocation in the future.

Examples of cases where a planned allocation will be canceled:

  • The job is modified, switched, stopped, or killed.
  • Some host of the future allocation is no longer usable. The host may have died, been closed, exceeded a load threshold, or the LSF daemons may be down.
  • A host of the allocation no longer satisfies the job’s requirements, such as the select requirement.
  • The estimated start time for the planned allocation has moved outside the planning window (default is 1 hour). For example, this could happen if higher priority jobs are started on the resources of the planned allocation.