The Cluster Manager server has a number of configuration properties that affect its behavior. These can be controlled using a grb_rsm.cnf configuration file. The installation package includes a predefined configuration file that can be used as a starting point (<installdir>/bin/grb_rsm.cnf).
The simplest way to modify the parameters is to edit the default configuration file. Other options are available, though. The grb_rsm process uses the following precedence rules:
- First priority: properties set with a command-line flag (using —config)
- Second priority: a configuration file in the current directory
- Third priority: a configuration file in a fixed, shared directory (C:\gurobi, /opt/gurobi, /Library/gurobi for Windows, Linux, and macOS platforms, respectively)
- Fourth priority: a configuration file in the directory where grb_rsm is located
Configuration file format
The configuration file contains a list of properties of the form PROPERTY=value. Lines that begin with the # symbol are treated as comments and are ignored. Here is an example:
# grb_rsm.cnf configuration file PORT=61080 CLUSTER_TOKEN=GRBTK-BzlUTKg9M/+HUvOpy/EPebc1CsttzOfdrfQshL4QkLm1FA== DB_URI=mongodb://127.0.0.1:27017While you could create this file from scratch, we recommend you start with the version that is included with the product and modify it instead.
grb_rsm properties command lists all of the available
properties, their default values, and provides documentation for each.
Some can be overridden on the
grb_rsm command line; the
grb_rsm properties command shows the name of the command-line
flag you would use. Here are some of the more important ones:
- The token is a private key that enables different nodes to join the same cluster. All nodes of a cluster and the Cluster Manager must have the same token. We recommended that you generate a brand new token when you set up your cluster. The grb_rs token command will generate a random token, which you can copy into the configuration file.
- This is the connection string to your database.
- This property indicates what port to use for HTTP or HTTPS communication between the clients and the Cluster Manager. By default, it will use the port 61080.
These properties let you configure some system-level options. You will find additional configuration properties in the settings page of the Cluster Manager. The settings are stored in the database and shared between the different Cluster Manager instances.