# Hot\_threads result shows WARM nodes are busy always

**URL:** <https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922>\
**Category:** Elasticsearch\
**Created:** [October 18, 2018, 1:21am UTC](https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922 "2018-10-18T01:21:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![af615dbd55cac2cacf32](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@af615dbd55cac2cacf32](https://discuss.elastic.co/u/af615dbd55cac2cacf32)\
**Post date:** [October 18, 2018, 1:21am UTC](https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922/1 "2018-10-18T01:21:31Z")

</div>

Hello,  
My Elasticsearch consists of 2masters(1 is active), 1client, 3HOT and 3WARM data nodes,m and Curator is running at 12PM for allocation / delete works.

I am observing **high CPU usage on all WARM nodes**.

01: Client  
02, 03: Master  
04, 05, 06: HOT  
07, 08, 09: WARM

I am attaching \_node/hot\_threads result on one of WARM node (07 data node) with $top result which captured at 10AM (No Curator runs yet today. It will run 2hours later); 08,09 nodes are the same way busy.  
As I mentioned, Curator works are not started yet, but hot\_threads results show "flush" to busy.

**Question:**  
Why WARM nodes are still busy to "flush" even though Curator run finished about 20hours ago? I expected WARM nodes are doing nothing after Curator work(allocation) is done, then they are busy only for "search" requests come. Is my understanding wrong?

Please help me to understand why WARM nodes are busy yet, and if there are any other commands to check the node status, please advise.

Thank you!

 ![top](https://us1.discourse-cdn.com/elastic/original/3X/0/6/06c7acc0a973504e09dba1f3f8c7da2d37661cf8.jpeg) ![hotthread01](https://us1.discourse-cdn.com/elastic/original/3X/e/c/eca4214dc1728ab0b82ccf63e0fedf17f178c060.jpeg) ![hotthread02](https://us1.discourse-cdn.com/elastic/original/3X/9/5/95143035a2a053df030e2b5b6b8266560b1c3e35.jpeg)

---

<div class="post-metadata">

**Author:** ![af615dbd55cac2cacf32](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@af615dbd55cac2cacf32](https://discuss.elastic.co/u/af615dbd55cac2cacf32)\
**Post date:** [October 25, 2018, 10:00am UTC](https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922/3 "2018-10-25T10:00:41Z")

</div>

any comments? please advise.

---

<div class="post-metadata">

**Author:** ![Admin\_Hack](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@Admin\_Hack](https://discuss.elastic.co/u/Admin_Hack)\
**Post date:** [October 25, 2018, 12:18pm UTC](https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922/4 "2018-10-25T12:18:57Z")

</div>

@Christian_Dahlqvist

---

<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 25, 2018, 12:21pm UTC](https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922/5 "2018-10-25T12:21:37Z")

</div>

Please do not ping people not already involved in the thread.

---

<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 22, 2018, 12:21pm UTC](https://discuss.elastic.co/t/hot-threads-result-shows-warm-nodes-are-busy-always/152922/6 "2018-11-22T12:21:37Z")

</div>

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