# Too many File Descriptors open **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2020, 5:57am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820 "2020-06-12T05:57:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Goutham\_Pratapa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goutham_pratapa/32/70208_2.png) [@Goutham\_Pratapa](https://discuss.elastic.co/u/Goutham_Pratapa)\ **Post date:** [June 12, 2020, 5:57am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/1 "2020-06-12T05:57:13Z")
Hi all, In our Dev-environment (ES single node setup) we have seen that the open `file descriptors for elastic search are 27491596`. ```auto (base) root@root:~$ lsof | awk '{print $2}'| uniq -c | sort -rn | head The output information may be incomplete. 27485413 3156 27000 2578 18432 2503 11400 9536 10584 4987 5684 15220 4902 1039 3840 23025 3720 23036 1084 22031 (base) root@root:~$ ps -eAf | grep 3156 root 3156 3100 28 Jun07 ? 1-10:07:07 /opt/jdk-12.0.1/bin/java -Xms4g -Xmx4g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=/tmp/elasticsearch-14429444041004318688 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=data -XX:ErrorFile=logs/hs_err_pid%p.log -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m -Djava.locale.providers=COMPAT -XX:UseAVX=2 -Des.cgroups.hierarchy.override=/ -Des.path.home=/usr/share/elasticsearch -Des.path.conf=/usr/share/elasticsearch/config -Des.distribution.flavor=default -Des.distribution.type=docker -cp /usr/share/elasticsearch/lib/* org.elasticsearch.bootstrap.Elasticsearch -Ediscovery.type=single-node ``` It looks way too much and as an ops person, it makes me worried to see this many file descriptors. Is there a way we can try and reduce this?? Can anyone please suggest a good approach to handle this kind of setup? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [June 12, 2020, 7:41am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/2 "2020-06-12T07:41:59Z")
This is not an accurate measurement since `lsof` reports each file descriptor multiple times, usually once per thread, and Elasticsearch has a lot of threads. ---
**Author:** ![Goutham\_Pratapa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goutham_pratapa/32/70208_2.png) [@Goutham\_Pratapa](https://discuss.elastic.co/u/Goutham_Pratapa)\ **Post date:** [June 12, 2020, 8:06am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/3 "2020-06-12T08:06:42Z")
sorry my bad ```auto (base) root@root:~$ sudo ls -l /proc/3156/fd | wc -l 164593 ``` above is the number ---
**Author:** ![Goutham\_Pratapa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goutham_pratapa/32/70208_2.png) [@Goutham\_Pratapa](https://discuss.elastic.co/u/Goutham_Pratapa)\ **Post date:** [June 12, 2020, 8:07am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/4 "2020-06-12T08:07:47Z")
```auto curl --request GET \ > --url http://localhost:9200/_nodes/stats/process {"_nodes":{"total":1,"successful":1,"failed":0},"cluster_name":"docker-cluster","nodes":{"jKhiPymDS1GPupuJoqgdOA":{"timestamp":1591949218940,"name":"jKhiPym","transport_address":"172.17.0.3:9300","host":"172.17.0.3","ip":"172.17.0.3:9300","roles":["master","data","ingest"],"attributes":{"ml.machine_memory":"67406077952","xpack.installed":"true","ml.max_open_jobs":"20","ml.enabled":"true"},"process":{"timestamp":1591949218941,"open_file_descriptors":164593,"max_file_descriptors":1048576,"cpu":{"percent":4,"total_in_millis":124889660},"mem":{"total_virtual_in_bytes":135503880192}}}}} ``` ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [June 12, 2020, 10:44am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/5 "2020-06-12T10:44:43Z")
That seems much more reasonable. Why is this causing a problem? ---
**Author:** ![Goutham\_Pratapa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/goutham_pratapa/32/70208_2.png) [@Goutham\_Pratapa](https://discuss.elastic.co/u/Goutham_Pratapa)\ **Post date:** [June 13, 2020, 8:15am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/6 "2020-06-13T08:15:56Z")
Was wondering if the number of file descriptors are okay for a single node ES setup and will this create bottle necks in the performance of a production machine which uses Intel® Xeon® Gold 6230 Processor. I think it wont create much of a chaos. Please correct me if im wrong . ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 11, 2020, 8:25am UTC](https://discuss.elastic.co/t/too-many-file-descriptors-open/236820/7 "2020-07-11T08:25:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.