# Elasticsearch bulk queue unbalanced, one node close to full

**URL:** <https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160>\
**Category:** Elasticsearch\
**Created:** [September 12, 2017, 6:17am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160 "2017-09-12T06:17:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![zuomang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zuomang/32/21991_2.png) [@zuomang](https://discuss.elastic.co/u/zuomang)\
**Post date:** [September 12, 2017, 6:17am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/1 "2017-09-12T06:17:46Z")

</div>

Recently we found one issue: our es cluster had three nodes which storage our product env log, one node of cluster bulk queue size always close to full, other nodes not.

i adjust our send client config file, remove the node and watch it. during some times, i found the node bulk queue size still close to full size.

Who can help solve this problem？

curl -s localhost:9200/\_cat/thread\_pool/bulk?h=id,host,name,active,queue,queue\_size,rejected  
node1 xxx bulk 0 0 3000 0  
node2 xxx bulk 0 0 3000 0  
node3 xxx bulk 9 1525 3000 1287

---

<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:** [September 12, 2017, 6:31am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/2 "2017-09-12T06:31:33Z")

</div>

How are you sending logs to Elasticsearch?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 12, 2017, 7:06am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/3 "2017-09-12T07:06:51Z")

</div>

What is the output of the [cat nodes API](https://www.elastic.co/guide/en/elasticsearch/reference/5.6/cat-nodes.html#cat-nodes)?

---

<div class="post-metadata">

**Author:** ![zuomang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zuomang/32/21991_2.png) [@zuomang](https://discuss.elastic.co/u/zuomang)\
**Post date:** [September 12, 2017, 7:41am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/4 "2017-09-12T07:41:31Z")

</div>

send client written by ourself, es driver is olivere/elastic.v5

---

<div class="post-metadata">

**Author:** ![zuomang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zuomang/32/21991_2.png) [@zuomang](https://discuss.elastic.co/u/zuomang)\
**Post date:** [September 12, 2017, 7:44am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/5 "2017-09-12T07:44:05Z")

</div>

sapadmin@ip-192-168-0-170 ~ $ curl localhost:9200/\_cat/nodes  
xxx 66 99 4 0.28 0.26 0.30 mdi \* xxxx  
xxx 59 93 9 0.34 0.52 0.60 mdi - xxxx  
xxx 57 98 21 1.50 1.49 1.56 mdi - xxxx

all instance type is 8c,30m

---

<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:** [September 12, 2017, 8:07am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/6 "2017-09-12T08:07:38Z")

</div>

Does that client do automatic load balancing?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 12, 2017, 10:44am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/7 "2017-09-12T10:44:18Z")

</div>

Are you inserting documents or performing updates? How many shards are you actively indexing into? How are these distributed across the cluster?

---

<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:** [October 10, 2017, 10:44am UTC](https://discuss.elastic.co/t/elasticsearch-bulk-queue-unbalanced-one-node-close-to-full/100160/8 "2017-10-10T10:44:22Z")

</div>

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