I'm not sure if it's considered a best practice to tweak the default /etc/sysconfig/graylog-server?
GRAYLOG_SERVER_JAVA_OPTS="-Xms2g -Xmx2g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled-XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow" But this at least seems to give you double the heap space. It's still not obvious how you should set mlockall. Or if I should even try. On Wednesday, March 25, 2015 at 7:31:38 PM UTC-7, Mark Moorcroft wrote: > > In looking at trying to increase the heap size today after a general > overhaul of our logging system I was reminded about a few things I never > seemed to get answers to in the past. Some of these statements are in fact > questions. > > Setting mlockall in elasticsearch apparently does NOT set it for graylog? > I can't seem to find a way to increase the heap size for the graylog index > beyond 972MB. > > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
