# Debugging extremely slow indexing **URL:** \ **Category:** Elasticsearch\ **Created:** [December 13, 2020, 4:00am UTC](https://discuss.elastic.co/t/debugging-extremely-slow-indexing/258498 "2020-12-13T04:00:50Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 13, 2020, 8:19pm UTC](https://discuss.elastic.co/t/debugging-extremely-slow-indexing/258498/9 "2020-12-13T20:19:44Z")
> [@Christian\_Dahlqvist](#): > > The hot threads output you shared indicates that the node is virtually idle All nodes look pretty idle except, strangely, `elasticsearch-elasticsearch-data-1b-12` which appears to have a number of threads busy writing to replicas. It is a bit suspicious that this one node is busy (but only a bit, I don't think it's worth following up right now). So I agree with what Christian said, the bottleneck appears to be outside the cluster. Try pushing it harder! I also note you're using the third-party ReadOnlyREST plugin. That isn't obviously a problem for you, but [it's been observed to cause problems for others](https://discuss.elastic.co/t/elasticsearch-master-node-jvm-reaching-99/241907/6). This is another reason to upgrade: security is included in the default (cost-free) basic license from 6.8 onwards so there's no need to rely on third parties for this feature any more. --- _[View the full topic](https://discuss.elastic.co/t/debugging-extremely-slow-indexing/258498)._