LS 2.0 & Java Memory Leak

[Kryten]

Hi,

Can someone please confirm whether or not the latest LS 2.1 release fixes the Java memory leak issue described here:

Logstash Memory leak?

Hello, We're running logstash 1.5.3 on windows 8.1 server 2012 having 8GB RAM. Logstash configured to have max 1g heap size. We're running quite a big job which runs for 10-12 hours to complete and creates multiple rolling logs with each processing thread. Logstash is pointing to logs folder and configured to parse it with each new line. Configuration settings for reference: input { file { path => "c:/temp/logs/*.txt" type => "somelogs" } } filter { if [type] == "somelogs" { grok { …

Since deploying LS 2.0 to a number of Windows machines I have been seeing the java.exe process regularly exceeding 2GB memory (private working set). This is crippling our expansion of the ELK stack into our infrastructure. We do use file/folder globbing in our paths...

Does 2.1 fix this?

Thanks,
Stuart

[Kryten]

Does not look like it is:

Issue: Memory leak in 1.5.3?

refers.