Logstash JVM heap filling up (dynamic field names)


(Exocomp) #1

Here is a summary of what I ran into, hopefully saves someone else some time.

Basically, there is a cache mechanism that logstash uses for string interpolation, there is a bug where random keys (or so it seems at the moment) are added to the cache, in my case there was no limit which ended up filling up the heap. For more info and my work around see the following:


(system) #2

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