Version: Filebeat beta1
I observe an insane memory footprint of filebeat beta1.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 23818 filebeat 15 -5 30.5g 27g 1556 S 13.9 57.6 593:35.22 filebeat
This is only after ~20hrs of process uptime. On this host I have four prospectors defined and they are scanning around 2000 files, which are in total worth less than 13GB.
Settings that might potentially be interesting:
harvester_buffer_size: 131072 publish_async: true
I see similar memory pattern across entire beta1 setup. Please let me know what info would be valuable for you to track issue. I did not observe this with alpha5.