# Filebeat rc1 resends full data set data upon random restart (registry file not updated properly)?

**URL:** <https://discuss.elastic.co/t/filebeat-rc1-resends-full-data-set-data-upon-random-restart-registry-file-not-updated-properly/63580>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 21, 2016, 8:00am UTC](https://discuss.elastic.co/t/filebeat-rc1-resends-full-data-set-data-upon-random-restart-registry-file-not-updated-properly/63580 "2016-10-21T08:00:09Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![shog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shog/32/12138_2.png) [@shog](https://discuss.elastic.co/u/shog)\
**Post date:** [October 27, 2016, 5:55pm UTC](https://discuss.elastic.co/t/filebeat-rc1-resends-full-data-set-data-upon-random-restart-registry-file-not-updated-properly/63580/13 "2016-10-27T17:55:06Z")

</div>

Ok, this is getting really interesting. Installing nightly build resulted in insane memory consumption (several dozens of gigabytes) and no events being delivered at all. Pretty much similar to what I've seen here: [Filebeat beta1: Insane memory footprint](https://discuss.elastic.co/t/filebeat-beta1-insane-memory-footprint/61998)

Would you be so kind to verify the config file that I've sent you yesterday?  
Maybe there is some value being misrepresented there?

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-rc1-resends-full-data-set-data-upon-random-restart-registry-file-not-updated-properly/63580)._