Try our new documentation site (beta).
Filter Content By
Version
Text Search
${sidebar_list_label} - Back
Filter by Language
Aborting Jobs
Jobs that are running on a Compute Server can be aborted by using the abort command. For example:
> grbcluster --server=server1 --password=admin 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 --server=server1 --password=pass 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 --server=server1 --password=pass 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 --server=server1 --password=admin abort 8f9b15d9If 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 recent command:
> grbcluster --server=server1 --password=pass recent JOBID ADDRESS STATUS STIME USER OPT 8f9b15d9 server1 ABORTED 2017-10-10 17:41:33 user1 OPTIMALAs you can see, the status of the job has changed to ABORTED.