2016-04-03 10:09:24 -04:00
|
|
|
[[file-descriptors]]
|
|
|
|
|
=== File Descriptors
|
|
|
|
|
|
2016-10-04 10:43:03 -04:00
|
|
|
[NOTE]
|
2016-10-10 08:47:25 -04:00
|
|
|
This is only relevant for Linux and macOS and can be safely ignored if running
|
|
|
|
|
Elasticsearch on Windows. On Windows that JVM uses an
|
|
|
|
|
https://msdn.microsoft.com/en-us/library/windows/desktop/aa363858(v=vs.85).aspx[API]
|
|
|
|
|
limited only by available resources.
|
2016-10-04 10:43:03 -04:00
|
|
|
|
2016-04-03 10:09:24 -04:00
|
|
|
Elasticsearch uses a lot of file descriptors or file handles. Running out of
|
|
|
|
|
file descriptors can be disastrous and will most probably lead to data loss.
|
|
|
|
|
Make sure to increase the limit on the number of open files descriptors for
|
|
|
|
|
the user running Elasticsearch to 65,536 or higher.
|
|
|
|
|
|
|
|
|
|
For the `.zip` and `.tar.gz` packages, set <<ulimit,`ulimit -n 65536`>> as
|
|
|
|
|
root before starting Elasticsearch, or set `nofile` to `65536` in
|
|
|
|
|
<<limits.conf,`/etc/security/limits.conf`>>.
|
|
|
|
|
|
|
|
|
|
RPM and Debian packages already default the maximum number of file
|
|
|
|
|
descriptors to 65536 and do not require further configuration.
|
|
|
|
|
|
|
|
|
|
You can check the `max_file_descriptors` configured for each node
|
|
|
|
|
using the <<cluster-nodes-stats>> API, with:
|
|
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
2016-08-26 16:18:58 -04:00
|
|
|
GET _nodes/stats/process?filter_path=**.max_file_descriptors
|
2016-04-03 10:09:24 -04:00
|
|
|
--------------------------------------------------
|
2016-08-26 16:18:58 -04:00
|
|
|
// CONSOLE
|
