After reading many conflicting ideas about how and where to set ES_HEAP_SIZE I'm resorting to asking here. Graylog says JVM is using xxx of 972MB. I changed the variable in /etc/sysconfig/elasticsearch and restarted both elasticsearch and graylog-server. The number remains constant. I believe I read elsewhere that changing that didn't work. I have given 6GB of memory to my Graylog 1.0.1 CentOS6 virtual machines. I was planning to try changing the heap number to 2g for a start. It seems to be working with 972, but now I'm trying to optimize. The suggested wisdom seems to be 50% of installed memory if I read it right. I'm hoping I don't have to start messing with /etc/sysconfig/graylog-server java options.
# Default Java options for heap and garbage collection. GRAYLOG_SERVER_JAVA_OPTS="-Xms1g -Xmx1g -XX:NewRatio=1 -XX:PermSize=128m -XX:MaxPermSize=256m -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled-XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow" I have some available memory left on my VM box if I should be increasing the 6GB to a larger amount (8G?). My current indices are at about 8 million records after quite a few months in operation. I have about 11 boxes sending syslog records. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
