# Unbalanced CPU load on every time

**URL:** <https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162>\
**Category:** Elasticsearch\
**Created:** [October 17, 2017, 3:35am UTC](https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162 "2017-10-17T03:35:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![YangYongZhi](https://avatars.discourse-cdn.com/v4/letter/y/7feea3/32.png) [@YangYongZhi](https://discuss.elastic.co/u/YangYongZhi)\
**Post date:** [October 17, 2017, 3:35am UTC](https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162/1 "2017-10-17T03:35:16Z")

</div>

There are 4 nodes in my cluster, like this:  
192.168.90.2 (master eligible : true, node: true)  
192.168.90.3 (master eligible : true, node: true)  
192.168.90.4 (master eligible : true, node: true)  
192.168.90.5 (master eligible : true, node: true)

and using '\_id' field as the routing field.

A index has 30,585,798 documents, and it's size is 30.67GB,

This index has 6 primary shards and 1 replica shard:  
shards: 6 \* 2

Many update requests will come on every day, then elasticsearch will do too many query operations, and gather it as a result list, and update them using bulk mode.

the client connects to this cluster on port 9300 as a transport node.

Problem : Only one node (192.168.90.5) load is very high every time. others had low CPU load.

Anybody can help me? thanks.

if you need more clues, I will supply them.

thanks again!

---

<div class="post-metadata">

**Author:** ![YangYongZhi](https://avatars.discourse-cdn.com/v4/letter/y/7feea3/32.png) [@YangYongZhi](https://discuss.elastic.co/u/YangYongZhi)\
**Post date:** [October 17, 2017, 3:47am UTC](https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162/2 "2017-10-17T03:47:46Z")

</div>

Elastic search version is 2.1.1

---

<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:** [October 17, 2017, 5:36am UTC](https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162/3 "2017-10-17T05:36:54Z")

</div>

Are you distributing requests evenly across all nodes? How are the primary shards distributed across the nodes?

---

<div class="post-metadata">

**Author:** ![YangYongZhi](https://avatars.discourse-cdn.com/v4/letter/y/7feea3/32.png) [@YangYongZhi](https://discuss.elastic.co/u/YangYongZhi)\
**Post date:** [October 17, 2017, 5:52am UTC](https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162/4 "2017-10-17T05:52:35Z")

</div>

No, I do not do anything for distributing request.

 ![51F1E067-3936-439D-A815-EED8194F99B9](https://us1.discourse-cdn.com/elastic/original/3X/a/6/a63a11c410413af44710def466e196a0b83822d0.jpg)

The node has very high CPU load is 192.168.90.73, and there is only one primary shard (shard #0) on it.

Only index 'dmall\_ware\_\_ware\_sku\_location' have many update requests on every day.

Thanks.

---

<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:** [November 14, 2017, 5:52am UTC](https://discuss.elastic.co/t/unbalanced-cpu-load-on-every-time/104162/5 "2017-11-14T05:52:53Z")

</div>

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