Client Commands¶
Once you have set up your client license file and started an Instant
Cloud instance, you can use grbcluster
to list the nodes in your
cluster or issue other client commands. Instances can be started by
submitting a job through the gurobi_cl
command-line tool, through
the Gurobi programming language APIs, or manually through the Instant
Cloud Manager website.
If you try to run grbcluster
without first starting an instance, you
will get the following error:
fatal : Instant Cloud pool default has no machines
If your instance is in the process of starting, you will get the following error:
fatal : Instant Cloud pool default is not ready
If your instance is up and running, grbcluster
will list the nodes
in your cluster:
> grbcluster nodes
ADDRESS STATUS TYPE GRP LICENSE #Q #R JL IDLE %MEM %CPU
ip-172-31-31-180 ALIVE COMPUTE m-HkQmbubhWH1g7m VALID 0 0 2 12m0s 27.08 1.98
ip-172-31-62-109 ALIVE COMPUTE m-HJSXmb_-2WBkLX VALID 0 0 2 12m0s 27.49 0.00
To obtain additional details (about the license file, the cloud pool, or
the name of the server), you can use the verbose mode with the -v
flag:
> grbcluster -v nodes
verb : Reading license file /licenses/gurobi.lic
verb : Accessing Instant Cloud pool 999999-pool5
verb : Using remote services on node ip-172-31-31-180
ADDRESS STATUS TYPE GRP LICENSE #Q #R JL IDLE %MEM %CPU
ip-172-31-31-180 ALIVE COMPUTE m-HkQmbubhWH1g7m VALID 0 0 2 12m0s 27.08 1.98
ip-172-31-62-109 ALIVE COMPUTE m-HJSXmb_-2WBkLX VALID 0 0 2 12m0s 27.49 0.00
You can use grbcluster
to perform most of the same
client commands on an Instant Cloud
cluster that you’d perform on a cluster running locally. You can monitor
running and recently processed jobs, access log files, view parameters,
etc.
However, you will not be able to execute administrative commands such as aborting a job, or changing the configuration of a node. To do so, please use the Instant Cloud Manager or the Instant Cloud REST API instead.