In the cluster, multiple Orchestrator server instances work together. If you have already set up a cluster of Orchestrator 5.5 server instances, you can upgrade the cluster to the latest Orchestrator version by upgrading its nodes.
- Stop all Orchestrator servers in the cluster.
- Upgrade one of the Orchestrator server instances in the cluster.
- Start the configuration service of the Orchestrator server you upgraded and log in to the configuration interface as vmware.
- Click Server Availability.
- Type values for the Cluster mode settings and click Apply changes.
Number of active nodes
The maximum number of active Orchestrator server instances in the cluster.
Active nodes are the Orchestrator server instances that run workflows and respond to client requests. If an active Orchestrator node stops responding, it is replaced by one of the inactive Orchestrator server instances.
The default number of active Orchestrator nodes in a cluster is one.
Heartbeat interval (milliseconds)
The time interval, in milliseconds, between two network heartbeats that an Orchestrator node sends to show that it is running.
The default value is 5000 milliseconds.
Number of failover heartbeats
The number of heartbeats that can be missed before an Orchestrator node is considered failed.
The default value is three heartbeats.
- Upgrade all other Orchestrator server instances in the cluster.
- Start all the Orchestrator nodes in the cluster.