Change cluster state
In the Status column, you can set a cluster to one of the following states: Running or Paused.
|
Cluster State |
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 is not allowed to finish all current executions. Cluster settings can be changed. For example, a database mapping can be changed. |
When you apply new settings to a cluster, the "Apply cluster settings" dialog box with options to proceed is shown.
Apart from Running and Paused, a cluster can have one of the following states:
-
Initializing
-
Shutting down
-
Invalid settings
-
Sending settings to RoboServer
-
Wait for schedules and robots to finish
-
Wait for currently running robots to finish
-
Stop all robots and schedules and apply settings immediately
The cluster states are 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 state. Therefore, the settings of a RoboServer can be updated while API robots are running. It is guaranteed, though, that robot settings are not updated during its execution. For example, if databases are updated while one or more API robots are running, the robots uses the databases that were configured when they started. Next time they are run, they use the new settings.