# Filebeat is using too much cpu

**URL:** <https://discuss.elastic.co/t/filebeat-is-using-too-much-cpu/187978>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 28, 2019, 6:33am UTC](https://discuss.elastic.co/t/filebeat-is-using-too-much-cpu/187978 "2019-06-28T06:33:14Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![fredrik.jonsson](https://avatars.discourse-cdn.com/v4/letter/f/c2a13f/32.png) [@fredrik.jonsson](https://discuss.elastic.co/u/fredrik.jonsson)\
**Post date:** [July 8, 2019, 10:20am UTC](https://discuss.elastic.co/t/filebeat-is-using-too-much-cpu/187978/6 "2019-07-08T10:20:54Z")

</div>

This seems to be related to this issue,

> [@CPU usage 100% when Elasticsearch is down](https://discuss.elastic.co/t/cpu-usage-100-when-elasticsearch-is-down/185850):
>
> I noticed that when Elasticsearch can't retrieve any more data the beats sending data went up to 100% CPU usage. E.g. if the disc is full on the Elasticsearch server. After clear up some space and "reset" Elasticsearch to be able to retrive data the CPU for the beats went down to normal behaviour. It is never OK to use that much CPU and risk the other process running on the same machine. Better loosing data than that the services stop working! Is this a bug or can I config the beats in a be…

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-is-using-too-much-cpu/187978)._