# Elasticsearch 1.7.4 only one node queue is full other is normal, maybe is a bug

**URL:** <https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759>\
**Category:** Elasticsearch\
**Created:** [April 8, 2016, 4:17am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759 "2016-04-08T04:17:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![whybangbang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whybangbang/32/7116_2.png) [@whybangbang](https://discuss.elastic.co/u/whybangbang)\
**Post date:** [April 8, 2016, 4:17am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759/1 "2016-04-08T04:17:19Z")

</div>

our's es' version is 1.7.4 ,today es-6 is down and is unavailable ,es-6'shard move to es-7 ,at this moment ,

[es-m-7] [14297421] Failed to execute fetch phase  
org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution (queue capacity 1000)

es-7' load is high but other node is normal and search queue is low

i think maybe is a bug,

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 8, 2016, 4:27am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759/2 "2016-04-08T04:27:07Z")

</div>

Why do you think it is a bug? Can you give us steps to replicate this behaviour to check if it is a bug?

Are you monitoring your hosts to see what is happening and why one is over loaded?

---

<div class="post-metadata">

**Author:** ![whybangbang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whybangbang/32/7116_2.png) [@whybangbang](https://discuss.elastic.co/u/whybangbang)\
**Post date:** [April 8, 2016, 4:34am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759/3 "2016-04-08T04:34:06Z")

</div>

![](https://us1.discourse-cdn.com/elastic/original/2X/0/0be9fe6dd999d0d39557f797861af85d4d985f31.png)  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/e/e7d13eb8ffe458a803c6dd3503c750e5bbb81f6b.png)

es-7 and es-5 is in a common cluster and have same number sahrd, but at 03:36 es-7'queue is full ,but es-5 is normal

 ![](https://us1.discourse-cdn.com/elastic/original/2X/f/f50486fd71ce2d0a54f6d1c2e57fb776208b7602.png)  
in normal case, search request should allocate to every node ，but in this monitor graph，all request route to es-7  
 ![](https://us1.discourse-cdn.com/elastic/original/2X/3/361950cb462f39d904eae56e0f1cc5dcd6ed6e9d.png)  
@warkolm

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 9, 2016, 12:40am UTC](https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759/4 "2016-04-09T00:40:57Z")

</div>

What's sending the searches to your cluster then?

---

<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:** [July 5, 2017, 11:01pm UTC](https://discuss.elastic.co/t/elasticsearch-1-7-4-only-one-node-queue-is-full-other-is-normal-maybe-is-a-bug/46759/5 "2017-07-05T23:01:03Z")

</div>