Platform LSF Reference Version 6.2
bbot
Platform LSF Reference
35
bbot
moves a pending job relative to the last job in the queue
SYNOPSIS
bbot job_ID | "job_ID[index_list]" [position]
bbot [-h | -V]
DESCRIPTION
Changes the queue position of a pending job, or a pending job array element, to affect
the order in which jobs are considered for dispatch.
By default, LSF dispatches jobs in a queue in the order of arrival (that is,
first-come-first-served), subject to availability of suitable server hosts.
The
bbot command allows users and the LSF administrator to manually change the
order in which jobs are considered for dispatch. Users can only operate on their own
jobs, whereas the LSF administrator can operate on any user’s jobs. Users can only
change the relative position of their own jobs.
If invoked by the LSF administrator,
bbot moves the selected job after the last job with
the same priority submitted to the queue. The positions of all users’ jobs in the queue
can be changed by the LSF administrator.
If invoked by a regular user,
bbot moves the selected job after the last job with the same
priority submitted by the user to the queue.
Pending jobs are displayed by
bjobs in the order in which they will be considered for
dispatch.
A user may use
bbot to change the dispatch order of their jobs scheduled using a
fairshare policy. However, if a job scheduled using a fairshare policy is moved by the LSF
administrator using
btop, the job will not be subject to further fairshare scheduling
unless the same job is subsequently moved by the LSF administrator using
bbot; in this
case the job will be scheduled again using the same fairshare policy (see the
FAIRSHARE
keyword in
lsb.queues(5) and HostPartition keyword in lsb.hosts(5)).
To prevent users from changing the queue position of a pending job with
bbot,
configure
JOB_POSITION_CONTROL_BY_ADMIN=Y in lsb.params.
OPTIONS
job_ID | "job_ID[index_list]"
Required. Job ID of the job or job array on which to operate.
For a job array, the index list, the square brackets, and the quotation marks are required.
An index list is used to operate on a job array. The index list is a comma separated list
whose elements have the syntax start_index[-end_index[
:step]] where start_index, end_index
and step are positive integers. If the step is omitted, a step of one is assumed. The job
array index starts at one. The maximum job array index is 1000. All jobs in the array
share the same job_ID and parameters. Each element of the array is distinguished by its
array index.