Alternative High Availability Setups
There are three principal alternative setups available for high-availability systems:
- Multi-tenant setup: two Orchestrators instances run on the same node. Each Orchestrator instance has its own access URL and config directory, but they share a database.
- Multiple Orchestrator nodes which operate independently. Tracking issues may be simpler in this case, because each node can run its own dedicated workflows. Note: In a setup with the Federated Workflow plugin, an Orchestrator node can coordinate workflows running on other (multiple, independent) Orchestrator nodes.
- Distributed architecture (MySQL running on a separate server from Orchestrator).
For example, you can have three Orchestrator servers (all active and running Orchestrator
and Apache services) and two MySQL servers (one running the MSQL service in active mode
and the other running in passive mode). Note the following requirements:
- No upward limit on the number of Orchestrator servers
- Maximum of two MySQL servers
- For boot or failure of Orchestrator servers, ACM controls the service restart
- For boot or failure of MySQL servers, ACM controls the MySQL failover and service restart