Hi gesman,
Unfortunately, there is no direct way to limit the memory usage of a forwarder.
But you can achieve it, if you make sure that your inputs are as limited as possible, e.g., point at single files or small directories with a few files and no subdirectories. You can reduce some memory by: shrinking maxQueueSize in outputs.conf to maybe 100 KB (vs a default of 500 KB)
Another thing you can do, is to tell OOM of your OS to be "nicer" to Splunk, even they don't recommend turning it off.
http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html
Regarding the auto-restart feature; How should this be handled by Splunk if it is killed by OOM? Create a agent-like wrapper script which checks if splunkd is running and if not, restart Splunk.
Hope this helps ...
cheers, MuS
... View more