# Indexing Causing Occasional Search Slowness

**URL:** <https://discuss.elastic.co/t/indexing-causing-occasional-search-slowness/175925>\
**Category:** Elasticsearch\
**Created:** [April 8, 2019, 10:13pm UTC](https://discuss.elastic.co/t/indexing-causing-occasional-search-slowness/175925 "2019-04-08T22:13:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![maembe](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@maembe](https://discuss.elastic.co/u/maembe)\
**Post date:** [April 8, 2019, 10:13pm UTC](https://discuss.elastic.co/t/indexing-causing-occasional-search-slowness/175925/1 "2019-04-08T22:13:15Z")

</div>

I have an search-heavy ES cluster with 5 data nodes and 3 masters. There is a single index with 5 shards and 1 replica each. There are about 3500 search operations per minute. 99% of the time it handles them really well and is incredibly fast. The CPU usage for each data node typically hovers around 35%. There are small indexing operations (all using the \_bulk apis to index in batches of 1500) happening semi-frequently without issue (10,000 or less docs). However, occasionally I'll have a batch of 100-150k documents (again, indexed in batches of 1500 at a time) which renders the cluster useless for searches for a few minutes until after it's finished. The CPU on each node will spike to 99% for the duration.

---

<div class="post-metadata">

**Author:** ![maembe](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@maembe](https://discuss.elastic.co/u/maembe)\
**Post date:** [April 10, 2019, 2:39pm UTC](https://discuss.elastic.co/t/indexing-causing-occasional-search-slowness/175925/2 "2019-04-10T14:39:57Z")

</div>

anyone?

---

<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:** [May 8, 2019, 2:40pm UTC](https://discuss.elastic.co/t/indexing-causing-occasional-search-slowness/175925/3 "2019-05-08T14:40:03Z")

</div>

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