Need help with other JFrog products?
Using the latest JFrog Mission Control version? See the documentation here.
How Elasticsearch is Packaged within Mission Control
Elasticsearch is packaged into the Mission Control installation. The following describes the different variations for each distribution package type:
|Docker||Elasticsearch for Docker is added as a Docker container to the Mission Control docker-compose project. This installs version 6.1.1.|
|Elasticsearch 6.1.1 is included in the Mission Control Debian project. Linux service files are added.|
|RPM||Elasticsearch 6.1.1 is included in the Mission Control RPM project. Linux service files are added.|
After Mission Control is fully installed, the Elasticsearch data files can be found in the following locations:
Elasticsearch uses the following communication ports:
Indexes and Aliases
There are two aliases to store and retrieve data:
|active_insight_data||Used point to active index to push data.|
|search_insight_data||Used to search and retrieve data|
On installation, these aliases and indices of format active_insight_data_timestamp* are created.
Mission Control is pre-configured to periodically cleanup indexes to keep data for a period of one year.
Setting Up a Cluster
As the amount of historical data collected by Mission Control accumulates, you may want to scale the Elasticsearch database used to store that data to maintain performance and responsiveness.
To scale a running Elasticsearch instance to a two-node cluster, follow the steps below:
Add the following settings to your startup scripts. In the case of a Docker installation, add them to the
docker-composefile, for a non-Docker installation, add them to the
Make sure to restart your first node before starting up the second one
First time you run Elasticsearch as a two-node cluster, you need to make sure to restart your first node (the one that already contains data) before adding the second one. Starting up the new node first could cause index mapping templates to be deleted.
- Start up the second node using the same configuration file (that you just modified) used for your first Elasticsearch node.
Once your cluster is set up, Mission Control will automatically detect the new node at runtime and start sending it requests.
Using a Load Balancer
If your Elasticsearch cluster is behind a load balancer, you need to add the following environment variables to the
insight_server service to provide it with the load balancer read and write URLs: