Elasticsearch prerequisites and system requirements
Make sure that your environment conforms to all prerequisites and system requirements.
Prerequisites
Jama Core must be running Jama Connect 8.10 or later, and is installed on a separate server from the Elasticsearch host.
System-compliant servers for Elasticsearch nodes (see the section Elasticsearch system requirements).
A license file for remote Elasticsearch.
During installation, the servers running Elasticsearch must be able to download and run the operator script from https://get.replicated.com/operator.
If Jama Core and Elasticsearch nodes are behind a proxy, you must add the Jama Core IP address to the NO_PROXY environment variable on each of the Elasticsearch nodes.
Port requirements
Jama Core host | Elasticsearch host |
|---|---|
9500 | 9200 |
9875–9880 | 9300 |
8125 |
This table illustrates how ports are used for communication between the main application server (Jama Core host) and nodes in the Elasticsearch cluster. Arrows (→, ↔) indicate the direction of communication between servers.
Description | TCP/UDP | Port range |
|---|---|---|
Jama Core → Elasticsearch node(s) | TCP | 9200 and 9300 |
Elasticsearch node(s) ↔ Elasticsearch node(s) | TCP | 9300 |
Elasticsearch node(s) → Jama Core | TCP | 9500 9874–9880 |
Elasticsearch node(s) → Jama Core | UDP | 8125 |
Elasticsearch system requirements
For a complete and current list of compatible operating systems in our most recent self-hosted release, see supported software.
Data size | Large | Enterprise |
|---|---|---|
CPU cores | 2 | 2 |
Total system RAM | 4 GB | 8 GB |
Elasticsearch Heap | 2 GB | 4 GB |
Disk Space | 25 GB | 100 GB |
Important
The Elasticsearch heap must be at least 50% less than the total system memory for the node. For example, if you have 6 GB of total system memory, Elasticsearch must have no more than 3 GB allocated to the heap.