# Elasticsearch coordinating node OOM/crash under sustained ingest (60k docs/min) with high shard count (~800) **URL:** \ **Category:** Elasticsearch\ **Created:** [June 4, 2026, 3:51am UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-oom-crash-under-sustained-ingest-60k-docs-min-with-high-shard-count-800/386710 "2026-06-04T03:51:57Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [June 4, 2026, 3:53am UTC](https://discuss.elastic.co/t/elasticsearch-coordinating-node-oom-crash-under-sustained-ingest-60k-docs-min-with-high-shard-count-800/386710/2 "2026-06-04T03:53:49Z")
Closed as duplicate of Please have patience when you are new and posting > [@Elasticsearch coordinating node OOM/crash under sustained ingest (60k docs/min) with high shard count (~800)](https://discuss.elastic.co/t/elasticsearch-coordinating-node-oom-crash-under-sustained-ingest-60k-docs-min-with-high-shard-count-800/386708): > > I have an Elasticsearch cluster with 3 master nodes, 1 data node, 1 ingest node, and 1 coordinating node. I also have 1 Kibana instance and 1 Fleet Server. Data ingestion is performed through approximately 12 Elastic Agents managed by Fleet. In the Fleet Server settings in Kibana, the server is pointing to the Fleet Server, and the output is configured to send data to the coordinating node. Currently, the cluster has around 800 shards, although disk usage is low (about 50 GB on the data node), … --- _[View the full topic](https://discuss.elastic.co/t/elasticsearch-coordinating-node-oom-crash-under-sustained-ingest-60k-docs-min-with-high-shard-count-800/386710)._