# Filebeat daemonset in Kubernetes is slow (or fails) to harvest logs from multiple pods

**URL:** https://discuss.elastic.co/t/filebeat-daemonset-in-kubernetes-is-slow-or-fails-to-harvest-logs-from-multiple-pods/322634
**Category:** Beats
**Tags:** filebeat
**Created:** [January 6, 2023, 5:56pm UTC](https://discuss.elastic.co/t/filebeat-daemonset-in-kubernetes-is-slow-or-fails-to-harvest-logs-from-multiple-pods/322634 "2023-01-06T17:56:05Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![melkamar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/melkamar/32/100785_2.png) [@melkamar](https://discuss.elastic.co/u/melkamar)
#### Post date: [January 10, 2023, 12:08pm UTC](https://discuss.elastic.co/t/filebeat-daemonset-in-kubernetes-is-slow-or-fails-to-harvest-logs-from-multiple-pods/322634/3 "2023-01-10T12:08:58Z")

</div>

Hi, sorry for taking a while to get back to this. I think this thread can be closed. I have talked to xeraa [at Slack](https://elasticstack.slack.com/archives/CNEDGGJQ3/p1673027496194389) and one part of the problem (the not receiving of logs) was fixed by upgrading to `8.5.3`.

The CPU/Mem usage was still high, but I managed to narrow that down to the Filebeat registry growing endlessly when containers are being restarted inside a pod. Created a separate issue about that [here](https://discuss.elastic.co/t/log-files-are-not-cleared-from-the-registry-when-harvested-kubernetes-container-is-restarted/322827).

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-daemonset-in-kubernetes-is-slow-or-fails-to-harvest-logs-from-multiple-pods/322634)._