# Indexing performance degrading over time

**URL:** <https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229>\
**Category:** Elasticsearch\
**Created:** [January 27, 2016, 12:30pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229 "2016-01-27T12:30:27Z")\
**Posts on this page:** 1\
**Showing post:** 44

<div class="post-metadata">

**Author:** ![Arun\_Agarwal](https://avatars.discourse-cdn.com/v4/letter/a/59ef9b/32.png) [@Arun\_Agarwal](https://discuss.elastic.co/u/Arun_Agarwal)\
**Post date:** [March 14, 2016, 5:21pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/44 "2016-03-14T17:21:31Z")

</div>

Yes i have seen the same thread stuck in this state.  
the only way to clear up this is to send a QUIT signal to the process.

But this does not explain why the issue was resolved after adding clientNodes ?

---

_[View the full topic](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229)._