We have a Graylog 2.0.2 (4da1379) setup which collects a very small amount of data (avg of 0 msg per minute), our sysadmin is complaining it's eating a lot of memory and it seems Graylog is spawning 170 child processes which are hogging memory.
Is it the expected behavior for Graylog to be spawning such a large amount of child processes? I went through the docs but couldn't find anything, however the threaddump available via the webinterface did have a large amount of threads in the 'waiting' status, e.g.
web-worker-15 id=236 state=WAITING
So is there something wrong with the setup, can we configure the number of threads somehow or should we just add more memory?