Change the Cluster Mode
You can set two different modes to a cluster: Running or Paused. The Paused mode is used to set clusters into a mode where nothing is run on them. The point is to be able to update cluster settings in a way that ensures that all robots in a given schedule use the same settings, and that settings are not changed in the middle of schedule runs. The table below explains the different modes.
|
Cluster Mode |
Description |
|---|---|
|
Running |
Cluster operates normally with schedules and individual robots executed as expected. Cluster settings are not "applied" to the RoboServers so that settings are not changed in the middle of schedule runs. |
|
Paused |
Cluster is not allowed to accept new execution requests and the RoboServers finish all current executions. Cluster settings can be changed. For example, a database mapping can be changed. |
-
Click
Change Cluster Mode above the cluster list.
The Change Cluster Mode window appears.
Note You can also right-click a cluster in the list and select the appropriate submenu item. - In the Cluster field, select the cluster to change.
-
In the
Cluster Mode field, select a Paused option to transition into Paused mode.
The cluster modes are, as the name implies, only relevant on a cluster level. As such, they are a way for the Management Console to control when tasks can be executed on clusters. They do not, however, control the individual RoboServers. This means that robots started from the API are not stopped when going into Paused mode. Therefore, the settings of a RoboServer can be updated while API robots are running. It is guaranteed, though, that a robot will not have its settings updated during its execution. For instance, if databases are updated while one or more API robots are running, the robots will use the databases that were configured when they started. Next time they are run, they will use the new settings.