Elasticsearch File Descriptors

By Opster Team

Updated: Mar 21, 2023

| 1 min read

Before you dig into the details of this technical guide, have you tried asking OpsGPT?

You'll receive concise answers that will help streamline your Elasticsearch/OpenSearch operations.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch/ OpenSearch operation.

What it means

File descriptors are required so that the Elasticsearch process can keep track of all the files it has open at any given time as well as all network connections to other nodes.

Running out of file descriptors would result in the Elasticsearch process not being able to keep track of the files it has open or not being able to open new files or socket connections when it needs to, and will most probably lead to data loss.

The Elasticsearch process should be permitted up to 65,536 or more.

How to resolve it

If you used systemd or yum to install Elasticsearch, then the setting should be applied automatically. If you installed a tarball then you will need to do the following:

Edit /etc/security/limits.conf 

Add the line:

elasticsearch - nofile 65535

MacOS users must also add the following line to the jvm.options file (not necessary for Linux):


Restart Elasticsearch.

You can check the setting has taken effect:

GET _nodes/stats/process?filter_path=**.max_file_descriptors

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch