# Unbalanced indexing load is it causing slow searches?

**URL:** <https://discuss.elastic.co/t/unbalanced-indexing-load-is-it-causing-slow-searches/79446>\
**Category:** Elasticsearch\
**Created:** [March 21, 2017, 3:07pm UTC](https://discuss.elastic.co/t/unbalanced-indexing-load-is-it-causing-slow-searches/79446 "2017-03-21T15:07:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![TealFawn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tealfawn/32/44845_2.png) [@TealFawn](https://discuss.elastic.co/u/TealFawn)\
**Post date:** [March 21, 2017, 3:07pm UTC](https://discuss.elastic.co/t/unbalanced-indexing-load-is-it-causing-slow-searches/79446/1 "2017-03-21T15:07:57Z")

</div>

We are having problems with slow searching and we are suspecting it has to do with our data node disproportionately handling the indexing load. What we see in our monitoring is this flip flopping of indexing rate between our data nodes.

 ![](https://us1.discourse-cdn.com/elastic/original/3X/6/b/6b5db7a6b1fcb9507a78b8593a6dfb46689fff51.jpg)  
 ![](https://us1.discourse-cdn.com/elastic/original/3X/1/3/130595daa6c2ec70ccf078031ca80d8f1a45c299.jpg)

I have a suspicion this is related to the following cluster setting.  
`cluster.routing.allocation.awareness.attributes: aws_availability_zone`

There are 4 data nodes in the cluster 2 per availability zone. The graphs above are from 2 nodes in the same AZ and the 2 other data nodes in the other AZ have the same pattern.

---

<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:** [April 18, 2017, 3:08pm UTC](https://discuss.elastic.co/t/unbalanced-indexing-load-is-it-causing-slow-searches/79446/2 "2017-04-18T15:08:09Z")

</div>

Closed on April 18, 2017, 3:08pm UTC

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