# Different process-model for ES node **URL:** \ **Category:** Elasticsearch\ **Created:** [April 27, 2013, 2:10pm UTC](https://discuss.elastic.co/t/different-process-model-for-es-node/11714 "2013-04-27T14:10:13Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Jaguar](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@Jaguar](https://discuss.elastic.co/u/Jaguar)\ **Post date:** [April 27, 2013, 2:10pm UTC](https://discuss.elastic.co/t/different-process-model-for-es-node/11714/1 "2013-04-27T14:10:13Z")
Hi, We have being using ES for a while, and it works great. But as the data accumulating, we are getting "too many open files" again. I understand this is actually something inherited from Lucene, and there is one option to use "compound" mode (one file per lucene index). Right now, each ES node is running as a single process. If we could fork multiple processes, with each process only holds a subset of shards. It should be possible to address "too many open files" in a scalable way. I'll willing to get my hands dirty for implementation, but would need some feedback about this idea. Thanks! Jaguar -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:39am UTC](https://discuss.elastic.co/t/different-process-model-for-es-node/11714/2 "2017-07-06T02:39:24Z")
Closed on July 6, 2017, 2:39am UTC