Mission Control supports a High Availability network configuration with a cluster of 2 or more, active/active nodes.
All cluster nodes in an HA configuration are synchronized, and jointly share and balance the workload between them. When a node becomes unavailable, the cluster will automatically spread the workload across the other remaining node(s) by leveraging the load balancer configuration.
Setting up several servers in an HA configuration is supported with an Enterprise licenseand provides the following benefits to your organization:
Ensures resilience and agility
Supports Active-active cluster
Easy to install and maintain
Supported an unlimited number of nodes
Mission Control seamlessly and instantly synchronizes all data, configuration, cached objects and scheduled job changes across all cluster nodes.
The Mission Control HA architecture consists of 3 layers: load balancer, application, local file system and external PostgreSQL and Elastic Search.
The load balancer is the entry point to your Mission Control HA cluster, optimally distributing requests to the running Mission Control nodes.
It is the responsibility of your organization to manage and configure it correctly.
Mission Control HA presents a cluster of two or more Mission Control nodes that share common resources. Each cluster node runs 4 micro services as in the Microservices and Ports section.
Local file system is used to store information specific to the node. The main file that is used here is the mc.key which is used to encrypt the database content. This need to be synchronized between the nodes manually.
Mission Control HA requires an external database, which is fundamental to management of Mission Control database and is also used to store cluster wide configuration files. Currently PostgreSQL is supported, and any change to configuration requires restarting all Mission Control nodes for changes to take effect.