# Not indexing fast enough but not using system resources

**URL:** <https://discuss.elastic.co/t/not-indexing-fast-enough-but-not-using-system-resources/64320>\
**Category:** Elasticsearch\
**Created:** [October 28, 2016, 6:41pm UTC](https://discuss.elastic.co/t/not-indexing-fast-enough-but-not-using-system-resources/64320 "2016-10-28T18:41:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maxwell\_Flanders](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@Maxwell\_Flanders](https://discuss.elastic.co/u/Maxwell_Flanders)\
**Post date:** [October 28, 2016, 6:41pm UTC](https://discuss.elastic.co/t/not-indexing-fast-enough-but-not-using-system-resources/64320/1 "2016-10-28T18:41:34Z")

</div>

I'm having a strange issue where we have a number of logstash instances that are slowing in throughput and outputting a bung of 429 errors (retrying failed action). In my experience this is because the cluster we are sending logs to is not indexing fast enough, or needs more resources to keep up. However our marvel output doesnt show any of the nodes in the cluster as low on resources, they are all running comfortably at 60-80% resources.

Do you know any ways I can investigate further what is happening here?? Thanks!

---

<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:** [July 5, 2017, 10:08pm UTC](https://discuss.elastic.co/t/not-indexing-fast-enough-but-not-using-system-resources/64320/2 "2017-07-05T22:08:40Z")

</div>

Closed on July 5, 2017, 10:08pm UTC