# High iops from filebeat
**URL:** https://discuss.elastic.co/t/high-iops-from-filebeat/334399
**Category:** Beats
**Tags:** filebeat
**Created:** [May 26, 2023, 6:37am UTC](https://discuss.elastic.co/t/high-iops-from-filebeat/334399 "2023-05-26T06:37:55Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@dimovvasiliy](https://discuss.elastic.co/u/dimovvasiliy)
#### Post date: [May 26, 2023, 6:37am UTC](https://discuss.elastic.co/t/high-iops-from-filebeat/334399/1 "2023-05-26T06:37:55Z")
Hi there!
I faced with a filebeat high io consumption problem. Sometimes some of my filebeat daemons start to make abnormal number of io requests (thousands per seond). I checked it and found that filebeat make a checkpoint by checkpoint, but log still 0 bytes size. Then I saw source code and found that there is a two conditions to make a [checkpoint](https://github.com/elastic/beats/blob/master/libbeat/statestore/backend/memlog/diskstore.go#L210): logInvalid flag is true and logfile reached some size. Log file is always zero size, and I decided that problem in logInvalid. logInvalid may set to true when occurs an error while read or write a logfile. I did a few experiments and found out that filebeat start a permanent checkpoint after sudden termination, in my case it happens quite often when hardware crashes or we force stop a k8s node.
After restart of filebeat it works normally
Is it a bug or normal behaviour?
Now I forced to watch on my io dashboard and restart filebeats few times a week, sounds boring
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 23, 2023, 8:38am UTC](https://discuss.elastic.co/t/high-iops-from-filebeat/334399/2 "2023-06-23T08:38:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.