# Filebeats high IO WAIT version 7.9.2

**URL:** <https://discuss.elastic.co/t/filebeats-high-io-wait-version-7-9-2/270575>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [April 19, 2021, 11:26am UTC](https://discuss.elastic.co/t/filebeats-high-io-wait-version-7-9-2/270575 "2021-04-19T11:26:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ankur\_Mahajan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankur_mahajan/32/45618_2.png) [@Ankur\_Mahajan](https://discuss.elastic.co/u/Ankur_Mahajan)\
**Post date:** [April 19, 2021, 11:26am UTC](https://discuss.elastic.co/t/filebeats-high-io-wait-version-7-9-2/270575/1 "2021-04-19T11:26:07Z")

</div>

We are randomly facing a weird issue of IO wait with filebeat 7.9.2. We have around 30 filebeat, metricbeat and heartbeat pipeline to an elasticsearch cluster. I searched this a lot but couldn't find a solution.

The ugly solution to this problem are below.

1. Stop the Filebeat service and delete the registry folder and start it again.
2. Uninstall and reinstall the Filebeat service.

I am using Ubuntu 18.04 EC2 machine with NVme.

Any help would be really appreciable.

 ![image (10)](https://us1.discourse-cdn.com/elastic/original/3X/2/e/2ef557944608540dc5312f91c82db31b28947d96.png)

---

<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:** [May 17, 2021, 1:26pm UTC](https://discuss.elastic.co/t/filebeats-high-io-wait-version-7-9-2/270575/2 "2021-05-17T13:26:11Z")

</div>

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