- Gurobi Compute Server 8.x
Someone opens a Gurobi Interactive Shell and starts a optimization run from it. After the run is completed, the person forgets about it and/or leave for a day. As long as this Interactive Shell is open one slot on the Gurobi Compute Server stays blocked.
Gurobi environments open a connection to the Compute Server, and, as long as the environment is active (not deleted or freed), the connection will stay open. A Gurobi Interactive Shell is an example of this. If you start a shell, you create a Gurobi environment, and it is not freed until you close the Interactive Shell.
Both Gurobi Compute Server and the Instant Cloud are based on Gurobi Remote Services (grb_rs).
Use the IDLETIMEOUT property of grb_rs to free the Gurobi Compute Server slot if it is not needed anymore. IDLETIMEOUT will terminate an idle job.
The behavior of this parameter is controlled by settings on the server side and on the client side. The purpose is for the server kill a job when it has sent no commands for a specified period of time. The property IDLETIMEOUT of grb_rs process controls this.
There are three ways to set the timeout:
1. On the client using the license file, specify IDLETIMEOUT: the value is expressed in seconds. Add a line like this to the license file:
to set the idle job timeout to 10 minutes.
2. On the client using the Gurobi API for the Environment object: Set the parameter CSIdleTimeout. Its value is expressed in seconds.
3. On the server you can use a grb_rs.cnf file to change the property IDLETIMEOUT.
The maximum of these values (the server setting and client setting) is used.