To get started, make sure your system complies with the above requirements and guidelines before you proceed to download and install Mission Control.
The general steps for installing Mission Control HA are:
|External Elasticsearch Cluster||Internal Elasticsearch Cluster|
mc.keyThe mc key is an internal secret, used by Mission Control to encrypt sensitive data and must be synced between the Mission Control cluster nodes. After the application is started, the mc key can be found in the following path: <JFMC_DATA>/security/mc.key.
For RPM and DEB installations, elasticsearch searchguard transport SSL certificates should be copied from first node to subsequent nodes. The certificates localhost.key ,localhost.pem and root-ca.pem are available in the Elasticsearch config folder of first node.
For the Docker Compose installation, use the Docker Compose file marked for HA post externalizing the database.
Add the following lines to the setenv.sh.
The additional cluster nodes should also be installed according to the general Mission Control installation instructions.
From Mission Control 3.4, if you already have a working standalone Mission Control environment.
The existing installation is considered the first cluster node followed by additional nodes that are then added to the HA environment.
Prior to installing the additional Mission Control nodes, perform the following: