# Elasticsearch Indexing Issues

**URL:** <https://discuss.elastic.co/t/elasticsearch-indexing-issues/326768>\
**Category:** Elasticsearch\
**Created:** [March 1, 2023, 2:03pm UTC](https://discuss.elastic.co/t/elasticsearch-indexing-issues/326768 "2023-03-01T14:03:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![H-Soni](https://avatars.discourse-cdn.com/v4/letter/h/90db22/32.png) [@H-Soni](https://discuss.elastic.co/u/H-Soni)\
**Post date:** [March 1, 2023, 2:03pm UTC](https://discuss.elastic.co/t/elasticsearch-indexing-issues/326768/1 "2023-03-01T14:03:54Z")

</div>

Hi,  
We have a 5-node cluster, currently running ES 5.6.11. When there's an increased load in indexing, heap usage reaches 90% in one of the nodes, while some have only 40-50% heap usage. Because of this, elasticsearch takes 70-80 seconds sometimes to index even 5-10 documents. We don't make the thread sleep after every bulk indexing. I am attaching a screenshot of heap, CPU & disk usage. Is there any way we can mitigate this issue? We have CMS GC as that is the only one supported in ES 5.6.11.

 ![Screenshot from 2023-03-01 19-34-41](https://us1.discourse-cdn.com/elastic/original/3X/1/4/14e8a2a89eabce060265aa5579bdb54a9c914256.png)

Is there any way to make the indexing faster? Our search is working just fine, as due to the index heavy load, we have increased refresh\_rate to 2s. Only indexing is causing issues now.

PS: 2nd Row is the current Master Node, with 75% heap usage

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 1, 2023, 11:54pm UTC](https://discuss.elastic.co/t/elasticsearch-indexing-issues/326768/2 "2023-03-01T23:54:56Z")

</div>

> [@H-Soni](#):
>
> currently running ES 5.6.11.

Please note that version is very much [EOL](https://www.elastic.co/support/eol) and no longer supported, you should be looking to upgrade as a matter of urgency. As such you are unlikely to get a resolution here other than to upgrade.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 29, 2023, 11:55pm UTC](https://discuss.elastic.co/t/elasticsearch-indexing-issues/326768/3 "2023-03-29T23:55:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.