brequeue

kills and requeues a job

Synopsis

brequeue [-J job_name | -J "job_name[index_list]"] [ -u user_name | -u all ] [ job_ID | "job_ID[index_list]"] [-d] [-e] [-r] [-a] [-H]
brequeue [-h | -V]

Description

You can only use brequeue on a job you own, unless you are root or the LSF administrator.

Kills a running (RUN), user-suspended (USUSP), or system-suspended (SSUSP) job and returns it to the queue. A job that is killed and requeued retains its submit time but is dispatched according to its requeue time. When the job is requeued, it is assigned the PEND status or PSUSP if the -H option is used. Once dispatched, the job starts over from the beginning. The requeued job keeps the same job ID.

When JOB_INCLUDE_POSTPROC=Y is set in lsb.params or in an application profile in lsb.applications, job requeue occurs only after post-execution processing, not when the job finishes.

Use brequeue to requeue job arrays or job array elements.

By default, kills and requeues your most recently submitted job when no job ID is specified.

With MultiCluster, you can only use brequeue on jobs in local queues. A job that is killed and requeued is assigned a new job ID on the cluster in which it is executed, but it retains the same job ID on the cluster from which it was submitted. For example, a job from cluster A that is killed and requeued and then run on cluster B is assigned a new job ID on cluster B. However, when the bjobs command is used from cluster A, the submitting cluster, the job is displayed with the original job ID. When the bjobs command is used from cluster B, the execution cluster, the job is displayed with the new job ID.

When absolute job priority scheduling (APS) is configured in the queue, all requeued jobs are treated as newly submitted jobs for APS calculation. The job priority, system, and ADMIN APS factors are reset on requeue.

When using multi-phase rusage resource requirement strings, such as with bsub -R, the requeued job is treated as a new job and resources are reserved from the beginning of the first phase.

Options

-a

Requeues all jobs including running jobs, suspending jobs, and jobs with EXIT or DONE status.

-d

Requeues jobs that have finished running with DONE job status.

-e

Requeues jobs that have terminated abnormally with EXIT job status.

-H

Requeues jobs to PSUSP job status.

-r

Requeues jobs that are running.

-J job_name | -J "job_name[index_list]"

Operates on the specified job.

The job name can be up to 4094 characters long. Job names are not unique.

The wildcard character (*) can be used anywhere within a job name, but cannot appear within array indices. For example job* returns jobA and jobarray[1], *AAA*[1] returns the first element in all job arrays with names containing AAA, however job1[*] will not return anything since the wildcard is within the array index.

-u user_name | -u all

Operates on the specified user’s jobs or all jobs. To specify a Windows user account, include the domain name in uppercase letters and use a single backslash (DOMAIN_NAME\user_name) in a Windows command line or a double backslash (DOMAIN_NAME\\user_name) in a UNIX command line.

Only root and LSF administrators can requeue jobs submitted by other users.

job_ID |"job_ID[index_list]"

Operates on the specified job or job array elements.

The value of 0 for job_ID is ignored.

-h

Prints command usage to stderr and exits.

-V

Prints LSF release version to stderr and exits.

Limitations

brequeue cannot be used on interactive batch jobs; brequeue only kills interactive batch jobs, it does not restart them.