# Very high CPU usage on one Elasticsearch data node **URL:** \ **Category:** Elasticsearch\ **Created:** [March 19, 2018, 12:17am UTC](https://discuss.elastic.co/t/very-high-cpu-usage-on-one-elasticsearch-data-node/124466 "2018-03-19T00:17:36Z")\ **Posts on this page:** 1\ **Showing post:** 15
**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:** [March 27, 2018, 8:01am UTC](https://discuss.elastic.co/t/very-high-cpu-usage-on-one-elasticsearch-data-node/124466/15 "2018-03-27T08:01:47Z")
I am not aware of any changes in load balancing. I do however have a few additional questions. Are you by any chance using preference for queries? If you just look at the larger indices, how are shards distributed across the nodes? Do the nodes with higher CPU usage by any chance have more of these shards? I also vaguely recall from [previous conversations](https://discuss.elastic.co/t/reindexing-indices-between-clusters/109316/31) that you were considering running updates in parallel to the full rebuilding of indices. If this is the case, do the nodes with higher CPU usage have more and/or larger primary shards than the other nodes? --- _[View the full topic](https://discuss.elastic.co/t/very-high-cpu-usage-on-one-elasticsearch-data-node/124466)._