The Orchestrator cluster provides not only high availability, but also load balancing when configured with NSX or another third-party load balancer. Orchestrator clustering is a zero-touch configuration, which means that the Orchestrator cluster is managing itself. The maximum number of active nodes that you define in the configuration dictates how many nodes are switched from standby to running. For example:
You define the number of active nodes as two; however, you configure three Orchestrator installations in this cluster and power them all on. This would result in two nodes being active and one being in standby mode.
If you now proceed to power off one of the active nodes, the standby node will become active. You could test this by setting the number of active nodes to
1
in the setup we are about to build.
There are certain drawbacks you should be aware of. It is not recommended to use the Orchestrator client to connect to the nodes running...