btop
Moves a pending job relative to the first job in the queue.
Synopsis
btop [-u] job_ID | "job_ID[index_list]" [position]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 their arrival (that is, first come, first served), subject to availability of suitable server hosts.
Use the btop command to manually change the order in which jobs are considered for dispatch. Users can operate only on their own jobs. LSF administrators can operate on any user’s jobs. Users can change the relative position only for their own jobs.
If the LSF administrator uses the btop command, the selected job is moved before the first job with the same priority that is submitted to the queue. The positions of all users’ jobs in the queue can be changed by the LSF administrator.
If a regular user uses the btop command, the selected job is moved before the first job with the same priority that is submitted by the user to the queue. Pending jobs are displayed by the bjobs command in the order in which they are considered for dispatch.
You can use the btop command to change the dispatch order of your jobs that was scheduled through a fair share policy. If the LSF administrator uses the btop command to move a job that was scheduled through a fair share policy, the job is not subject to further fair share scheduling unless the same job is later moved by the LSF administrator with the bbot command. In this case, the job is scheduled again by using the same fair share policy.
To prevent users from changing the queue position of a pending job with the btop command, configure the JOB_POSITION_CONTROL_BY_ADMIN=Y in the lsb.params file.
You cannot run the btop command on jobs that are pending in an absolute priority scheduling (APS) queue.
Options
- -u
- Optional. When specified, allows jobs to be moved relative to the normal user's own job list. This option can only be used by the LSF administrator. If used by a normal user, this option is ignored.
- job_ID | "job_ID[index_list]"
- Required. Job ID of the job or of the 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 have the same job ID and parameters. Each element of the array is distinguished by its array index.
- position
- Optional. The position argument can be specified to indicate where in the queue the job is to be placed. The position option is a positive number that indicates the target position of the job from the beginning of the queue. The positions are relative to only the applicable jobs in the queue, depending on whether the invoker is a regular user or the LSF administrator. The default value of 1 means the position is before all the other jobs in the queue that have the same priority.
- -h
- Prints command usage to stderr and exits.
- -V
- Prints LSF release version to stderr and exits.
See also
bbot, bjobs, bswitch.