Services Stack for the Orchestrator Nodes

Regardless of which architecture is deployed, both Orchestrator nodes are considered active because clients can contact any of them to access the web application portion or the transfer server portion. Nevertheless, not all of the Aspera services run at the same time on both machines.

While some services are considered active/active and do run on both nodes, other services are considered active/passive and only run on one of the two nodes. The node that runs all the services is called the active node, and the node that only runs the active/passive services is called the passive node.

Figure: Orchestrator Services Stack Interacting with the Shared Storage

The mysql service runs only on the active node. While both nodes can access the ACM files and Orchestrator packages simultaneously (read-write mode), the MySQL data files are accessed at a specific time by a single instance of the MySQL service running on the active node.