Try our new documentation site (beta).
CSIdleTimeout
Idle time before Compute Server kills a job
| Type: | int | |
|---|---|---|
| Default value: | -1 | |
| Minimum value: | -1 | |
| Maximum value: | MAXINT |
This parameter allows you to set a limit on how long a Compute Server job can sit idle before the server kills the job (in seconds). A job is considered idle if the server is not currently performing an optimization and the client has not issued any additional commands.
The default value will allow a job to sit idle indefinitely in all but a few circumstances. The first exception is the Gurobi Instant Cloud, where the default setting will automatically impose a 30 minute idle time limit (1800 seconds). If you are using an Instant Cloud pool, the actual value will be the maximum between this parameter value and the idle timeout defined by the pool.
The second exception is any program that uses the Gurobi Python interface (including the Gurobi Interactive Shell). Such programs will also get a 30 minute idle time limit by default.
You must set this parameter through either a gurobi.lic file
(using IDLETIMEOUT=n) or an empty
environment. Changing the parameter after
your environment has been created will have no effect.
Refer to the Gurobi Remote Services Reference Manual for more information on starting Compute Server jobs.
One important note about integer-valued parameters: while the maximum
value that can be stored in a signed integer is 
, we use a
MAXINT value of 2,000,000,000. Attempting to set an integer
parameter to a value larger than this maximum will produce an error.
For examples of how to query or modify parameter values from our different APIs, refer to our Parameter Examples.
