# High CPU on master and client nodes only when indexing

**URL:** https://discuss.elastic.co/t/high-cpu-on-master-and-client-nodes-only-when-indexing/122984
**Category:** Elasticsearch
**Created:** [March 7, 2018, 11:55pm UTC](https://discuss.elastic.co/t/high-cpu-on-master-and-client-nodes-only-when-indexing/122984 "2018-03-07T23:55:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Eduard\_Dudar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eduard_dudar/32/2845_2.png) [@Eduard\_Dudar](https://discuss.elastic.co/u/Eduard_Dudar)
#### Post date: [March 7, 2018, 11:55pm UTC](https://discuss.elastic.co/t/high-cpu-on-master-and-client-nodes-only-when-indexing/122984/1 "2018-03-07T23:55:28Z")

</div>

I'm trying to track down a problem when CPU load on dedicated coordinating and master nodes closely follows indexing activity under some unclear yet circumstances. From what I know about these two types, they should not experience any significant load when indexing is happening, unless maybe when data mappings change significantly with a large number of different fields coming in with every document. That's not the case however and I don't see this all the time. Any idea what specific type of activity can cause such synchronous jumps?

![Screen_Shot_2018-03-07_at_3_48_27_PM](https://us1.discourse-cdn.com/elastic/original/3X/a/6/a6e529fec3f0605f1ae83e48cce7b5452dbe5e25.png)

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: [April 4, 2018, 11:55pm UTC](https://discuss.elastic.co/t/high-cpu-on-master-and-client-nodes-only-when-indexing/122984/2 "2018-04-04T23:55:57Z")

</div>

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