# Distributed query avoiding one node?

**URL:** <https://discuss.elastic.co/t/distributed-query-avoiding-one-node/68825>\
**Category:** Elasticsearch\
**Created:** [December 13, 2016, 7:58am UTC](https://discuss.elastic.co/t/distributed-query-avoiding-one-node/68825 "2016-12-13T07:58:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dandrestor](https://avatars.discourse-cdn.com/v4/letter/d/7cd45c/32.png) [@dandrestor](https://discuss.elastic.co/u/dandrestor)\
**Post date:** [December 13, 2016, 7:58am UTC](https://discuss.elastic.co/t/distributed-query-avoiding-one-node/68825/1 "2016-12-13T07:58:04Z")

</div>

Hi,

I have a cluster with three elasticsearch nodes, and I'm running a query that returns a _lot_ of hits, via Kibana. The indexes hit by the search are using the default settings of 5 shards, 1 replica; the shards are distributed more or less evenly across the three nodes.

Now due to the large amount of data, the search takes long to execute. Out of curiosity, I checked the three nodes, and I noticed that two of them have a noticeable increase in CPU utilization while executing the search, while the third does not. ( **Update:** I see the same pattern with IO activity.) Could it be the case that the query is being distributed to shards residing only on the two nodes, while the third is omitted for some reason?

Thanks,  
Dan

---

<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:** [January 10, 2017, 7:58am UTC](https://discuss.elastic.co/t/distributed-query-avoiding-one-node/68825/2 "2017-01-10T07:58:04Z")

</div>

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