# Bulk indexing causes management threadpool queue to skyrocket

**URL:** <https://discuss.elastic.co/t/bulk-indexing-causes-management-threadpool-queue-to-skyrocket/217852>\
**Category:** Elasticsearch\
**Created:** [February 4, 2020, 4:58pm UTC](https://discuss.elastic.co/t/bulk-indexing-causes-management-threadpool-queue-to-skyrocket/217852 "2020-02-04T16:58:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Doc\_Kaos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/doc_kaos/32/53671_2.png) [@Doc\_Kaos](https://discuss.elastic.co/u/Doc_Kaos)\
**Post date:** [February 4, 2020, 10:16pm UTC](https://discuss.elastic.co/t/bulk-indexing-causes-management-threadpool-queue-to-skyrocket/217852/6 "2020-02-04T22:16:04Z")

</div>

I did see another post you made here @DavidTurner [Concurrent Indices stats requests cause cluster to go red](https://discuss.elastic.co/t/concurrent-indices-stats-requests-cause-cluster-to-go-red/161385)

Which gave us the hint to turn off `--es.indices` from the exporter. But we are still seeing all these `CompletionStats` ... is there a way to turn off anything to do with completion completely? (Beside staying on ES 2 😉)

---

_[View the full topic](https://discuss.elastic.co/t/bulk-indexing-causes-management-threadpool-queue-to-skyrocket/217852)._