# High OS Cpu usage on 7.7.1

**URL:** https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301
**Category:** Elasticsearch
**Created:** [June 23, 2020, 4:25pm UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301 "2020-06-23T16:25:07Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![chakragod](https://avatars.discourse-cdn.com/v4/letter/c/5f9b8f/32.png) [@chakragod](https://discuss.elastic.co/u/chakragod)
#### Post date: [June 23, 2020, 4:25pm UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/1 "2020-06-23T16:25:07Z")

</div>

Hello,

We recently upgraded our ELK stack from v 7.4.0 to 7.7.1 and now we noticed that the OS CPU is 100% on our hot data nodes which do the indexing. The OS CPU is almost always at 100%, the process CPU is close to 45-50%.

We checked the hot threads and saw 98% of the times it is Lucene Merging Thread. The refresh interval on our indices is 120s, size is 100gb (3 shards).

Is this a bug in 7.7.1? Or are we doing something wrong? This was not the case in previous versions.

Thank you.

---

<div class="post-metadata">

### Author: ![Sc7565](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sc7565/32/70485_2.png) [@Sc7565](https://discuss.elastic.co/u/Sc7565)
#### Post date: [June 25, 2020, 2:43pm UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/2 "2020-06-25T14:43:36Z")

</div>

we are also facing same issue, on indexing nodes

---

<div class="post-metadata">

### Author: ![chakragod](https://avatars.discourse-cdn.com/v4/letter/c/5f9b8f/32.png) [@chakragod](https://discuss.elastic.co/u/chakragod)
#### Post date: [June 26, 2020, 3:04pm UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/3 "2020-06-26T15:04:36Z")

</div>

Another piece of information is:  
I tried downgrading our cluster with the exact config to 7.4.0, and the CPU looks perfectly fine now.  
Which makes me wonder if it is something in 7.7.1 which is maybe reporting incorrect metrics?

---

<div class="post-metadata">

### Author: ![Sc7565](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sc7565/32/70485_2.png) [@Sc7565](https://discuss.elastic.co/u/Sc7565)
#### Post date: [July 14, 2020, 11:50am UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/4 "2020-07-14T11:50:45Z")

</div>

We also concluded with same results, seems something off in 7.6 and 7.7 releases

---

<div class="post-metadata">

### Author: ![Ignacio\_Vera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ignacio_vera/32/36674_2.png) [@Ignacio\_Vera](https://discuss.elastic.co/u/Ignacio_Vera)
#### Post date: [July 14, 2020, 1:14pm UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/5 "2020-07-14T13:14:27Z")

</div>

I am wondering if the problem you are experiencing is due to wrong JVM settings after upgrading. See: [Elasticsearch 7.8 worse heap management](https://discuss.elastic.co/t/elasticsearch-7-8-worse-heap-management/240996/14)

---

<div class="post-metadata">

### Author: ![Steve\_Mushero](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steve_mushero/32/22441_2.png) [@Steve\_Mushero](https://discuss.elastic.co/u/Steve_Mushero)
#### Post date: [July 16, 2020, 6:20am UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/6 "2020-07-16T06:20:50Z")

</div>

Yeah, any GC going on? If not, this seems odd unless there was merge behavior / scheduling changes (can only limit thread count) , but doubt anything big between 7.4. and 7.7 - you could try to tune merging just to see if that's the issue - and also upgrade to 7.8 to see if helps.

Any change to templates, especially for refresh rate?

---

<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: [August 13, 2020, 6:20am UTC](https://discuss.elastic.co/t/high-os-cpu-usage-on-7-7-1/238301/7 "2020-08-13T06:20:53Z")

</div>

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