# Filebeat kubernetes reuse inode

**URL:** <https://discuss.elastic.co/t/filebeat-kubernetes-reuse-inode/273390>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [May 19, 2021, 10:55am UTC](https://discuss.elastic.co/t/filebeat-kubernetes-reuse-inode/273390 "2021-05-19T10:55:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mafr](https://avatars.discourse-cdn.com/v4/letter/m/f19dbf/32.png) [@mafr](https://discuss.elastic.co/u/mafr)\
**Post date:** [May 19, 2021, 10:55am UTC](https://discuss.elastic.co/t/filebeat-kubernetes-reuse-inode/273390/1 "2021-05-19T10:55:36Z")

</div>

Hello,

i have got a kubernetes enviroment (v1.19.2) with some deployments.

Filebeat autodiscover properly "detects" log files, but after first log collect , filebeat are not harvest log files again (maybe after some time?)  
Probably it is due to inode reuse on docker log file.  
I'm using ext4 filesystem

Docker daemon.json

```auto
 max-files = 1, 
 max-size = 100M

```

Filebeat.yml properties:

```auto
    filebeat.autodiscover:
      providers:
        - type: kubernetes
          node: ${HOSTNAME}
          ignore_older: 1s
          scan_frequency : 1s
          clean_inactive: 3s

```

How I can deal with inode reuse?  
Filebeat can deal with 40k log lines per second?  
Docker can reach max file size in 10s  
As output i'm using logstash

ELKF 7.12.0

---

<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:** [June 16, 2021, 12:56pm UTC](https://discuss.elastic.co/t/filebeat-kubernetes-reuse-inode/273390/2 "2021-06-16T12:56:31Z")

</div>

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