This version of the OpenSearch documentation is no longer maintained. For the latest version, see the current documentation. For information about OpenSearch version maintenance, see Release Schedule and Maintenance Policy.
This section details how to install OpenSearch on your host, including which operating systems are compatible with OpenSearch, which ports to open, and which important settings to configure on your host.
Operating system compatibility
We recommend installing OpenSearch on Red Hat Enterprise Linux (RHEL) or Debian-based Linux distributions that use systemd, such as CentOS, Amazon Linux 2, or Ubuntu Long-Term Support (LTS). OpenSearch should work on most Linux distributions, but we only test a handful. We recommend RHEL 7 or 8, CentOS 7 or 8, Amazon Linux 2, or Ubuntu 16.04, 18.04, or 20.04 for any version of OpenSearch. OpenSearch also supports Windows Server 2019.
File system recommendations
Avoid using a network file system for node storage in a production workflow. Using a network file system for node storage can cause performance issues in your cluster due to factors such as network conditions (like latency or limited throughput) or read/write speeds. You should use solid-state drives (SSDs) installed on the host for node storage where possible.
The OpenSearch distribution for Linux ships with a compatible Adoptium JDK version of Java in the
jdk directory. To find the JDK version, run
./jdk/bin/java -version. For example, the OpenSearch 1.0.0 tarball ships with Java 15.0.1+9 (non-LTS), OpenSearch 1.3.0 ships with Java 184.108.40.206+1 (LTS), and OpenSearch 2.0.0 ships with Java 17.0.2+8 (LTS). OpenSearch is tested with all compatible Java versions.
|OpenSearch Version||Compatible Java Versions||Bundled Java Version|
|1.0 - 1.2.x||11, 15||15.0.1+9|
|1.3.x||8, 11, 14||220.127.116.11+1|
To use a different Java installation, set the
JAVA_HOME environment variable to the Java install location. For example:
The following ports need to be open for OpenSearch components.
|Port number||OpenSearch component|
|443||OpenSearch Dashboards in AWS OpenSearch Service with encryption in transit (TLS)|
|9200||OpenSearch REST API|
|9300||Node communication and transport|
For production workloads, make sure the Linux setting
vm.max_map_count is set to at least 262144. Even if you use the Docker image, set this value on the host machine. To check the current value, run this command:
To increase the value, add the following line to
sudo sysctl -p to reload.
The sample docker-compose.yml file also contains several key settings:
Disables swapping (along with
memlock). Swapping can dramatically decrease performance and stability, so you should ensure it is disabled on production clusters.
Sets the size of the Java heap (we recommend half of system RAM).
Sets a limit of 65536 open files for the OpenSearch user.
Allows you to access Performance Analyzer on port 9600.
Do not declare the same JVM options in multiple locations because it can result in unexpected behavior or a failure of the OpenSearch service to start. If you declare JVM options using an environment variable, such as
OPENSEARCH_JAVA_OPTS=-Xms3g -Xmx3g, then you should comment out any references to that JVM option in
config/jvm.options. Conversely, if you define JVM options in
config/jvm.options, then you should not define those JVM options using environment variables.