# High CPU iowaitT time

**URL:** <https://discuss.elastic.co/t/high-cpu-iowaitt-time/156828>\
**Category:** Elasticsearch\
**Created:** [November 15, 2018, 9:54am UTC](https://discuss.elastic.co/t/high-cpu-iowaitt-time/156828 "2018-11-15T09:54:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![raghunadh.parlapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raghunadh.parlapalli/32/37673_2.png) [@raghunadh.parlapalli](https://discuss.elastic.co/u/raghunadh.parlapalli)\
**Post date:** [November 15, 2018, 9:54am UTC](https://discuss.elastic.co/t/high-cpu-iowaitt-time/156828/1 "2018-11-15T09:54:37Z")

</div>

Hi,

Did any one come accross this situation? and any ideas to fix it?

we have Grafana (2 nodes) + ElasticSearch (3 master and 2 data nodes) Integration environment.

ElasticSearch nodes peformance metrics are configured on Grafana.

we have problem recently with ssd disks and it has been fixed. so we tried to add data node 6 back on to cluster, but it still causes heavy cpu iowait time.

any suggestions/tools to investigate and to identify what is the reason for high iowait time?

---

<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:** [December 13, 2018, 10:08am UTC](https://discuss.elastic.co/t/high-cpu-iowaitt-time/156828/2 "2018-12-13T10:08:01Z")

</div>

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