Submitting a re-sizable job

Procedure

  1. Run bsub –n 4,10 -ar -app application_profile_name

    LSF dispatches the job to the specified application profile that is configured for re-sizable jobs (as long as the minimum task request is satisfied).

    After the job successfully starts, LSF continues to schedule and allocate additional resources to satisfy the maximum task request for the job.

  2. (Optional, as required) Release resources that are no longer needed.

    bresize release released_host_specification job_ID

    where released_host_specification is the specification (list or range of hosts and number of tasks) of resources to be released.

    For example,

    bresize release "1*hostA 2*hostB hostC" 221

    LSF releases 1 task on hostA, 2 tasks on hostB, and all tasks on hostC for job 221.

    Result: The resize notification command runs on the first execution host.

  3. (Optional, as required) Request additional tasks to be allocated to jobs that require more resources.

    bresize request [min_tasks,] tasks job_ID

    where
    • tasks is the total number of tasks to allocate to the jobs.
    • min_tasks is the minimum number of tasks to allocate to the jobs.
    If min_tasks is specified, LSF pends the request until the minimum number of tasks can be added to the job, otherwise, LSF pends the request until the full total number of tasks is available. Specifying a minimum number of tasks allows the request to grow the task allocation partially, otherwise the request requires the entire maximum number to be allocated at once.

    For example,

    bresize request 10 221

    This command requests a total of 10 tasks to be added to job 221. If LSF cannot add 10 tasks to the job, the request pends.

    bresize request 4,10 221

    This command requests a minimum of 4 and a total of 10 tasks to be added to job 221. The request pends if LSF cannot add at least 4 tasks to the job. The request can add additional tasks up to a total of 10. Therefore, if LSF initially adds 7 tasks to the job, the remaining 3 tasks requested remain pending.

    Result: The resize notification command runs on the first execution host.