Documentation

Aborting Jobs

Jobs that are running on a Compute Server can be aborted by using the job abort command. For example:

> grbcluster job abort e7022667

The following steps illustrate how you would start and subsequently abort a job. First, use the Gurobi command-line tool (gurobi_cl) to start a long-running optimization job on your Compute Server:

> gurobi_cl glass4.mps

Once the job starts, you can use the grbcluster jobs command to retrieve the associated JOBID (or you can read it off from the output of gurobi_cl):

> grbcluster jobs
JOBID    ADDRESS STATUS  #Q  STIME               PRIO
8f9b15d9 server1 RUNNING     2017-10-10 17:30:33 0

The full or short JOBID can be used to abort the job as follows:

> grbcluster job abort 8f9b15d9

If no JOBID is specified, the most recently started job will be aborted.

After the abort command is issued, the status of the job can be retrieved using the job recent command:

> grbcluster job recent
JOBID    ADDRESS  STATUS  STIME               USER  OPT
8f9b15d9 server1  ABORTED 2017-10-10 17:41:33 user1 OPTIMAL

As you can see, the status of the job has changed to ABORTED.