I would also like to know if this affects the WebUI, beacause i have taken several measures to set ES_HEAP_SIZE, ES_MIN_MEM, ES_MAX_MEM and do NOT see a change in the WebUI. I'm beginning to think, the WebUI is solely for the graylog services, not ElasticSearch.
On Thursday, November 19, 2015 at 3:47:51 PM UTC-6, Matthew Simon wrote: > > HI > > Does this fix update the web interface. > > Or does it remain to state bellow. > > The JVM is using * 159.3 MB of 972.8 MB* heap space and will not attempt > to use more than * 1.4 GB* > > > On Thursday, June 20, 2013 at 12:15:20 AM UTC+2, lennart wrote: >> >> Increasing the graylog2-server heap size can be necessary especially >> in high volume setups. The way you solved it is the currently >> officially recommended way! :) >> >> Cheers, >> Lennart >> >> >> On Wed, Jun 19, 2013 at 5:20 PM, Alex B. <[email protected]> wrote: >> > I don't know then ... i thought you were running a standalone server >> > (Graylog2 + ES), like i do. I had out of memory errors too and resolved >> it >> > increasing ES (not the graylog2 one) heap size. >> > >> > Le mardi 18 juin 2013 19:28:27 UTC+2, Christian Hedegaard a écrit : >> >> >> >> Since Graylog is using the embedded ES client, how would that work? We >> >> have a pretty big 5-node ES cluster running on AWS m1.xl’s and do not >> run >> >> ANY ES on the graylog server itself, except for the embedded one which >> we >> >> have no choice over. >> >> >> >> >> >> >> >> We’re using 12RC of Graylog2 >> >> >> >> >> >> >> >> From: Alex B. [mailto:[email protected]] >> >> >> >> Sent: Tuesday, June 18, 2013 4:34 AM >> >> To: [email protected] >> >> >> >> Cc: Christian Hedegaard >> >> Subject: Re: Setting graylog2's heap size. >> >> >> >> >> >> >> >> I think your memory errors were generated by ES, not graylog2, there's >> >> nothing to change in graylog2 script. Tune ES heap size instead. >> >> >> >> Le lundi 17 juin 2013 20:52:32 UTC+2, Christian Hedegaard a écrit : >> >> >> >> Is there a “correct” way to set the heap size for graylog2? I just >> >> manually edited the graylog2ctl script like so: >> >> >> >> >> >> >> >> HEAP_SIZE='-Xms8192M -Xmx8192M' >> >> >> >> >> >> >> >> start() { >> >> >> >> echo "Starting graylog2-server ..." >> >> >> >> cd "$GRAYLOG2CTL_DIR/.." >> >> >> >> $NOHUP java ${HEAP_SIZE} -jar ${GRAYLOG2_SERVER_JAR} -f >> >> ${GRAYLOG2_CONF} -p ${GRAYLOG2_PID} >> ${LOG_FILE} & >> >> >> >> } >> >> >> >> >> >> >> >> But I wanted to make sure there wasn’t a more “official” way to do it >> like >> >> it picking up some environment variables or other process. >> >> >> >> >> >> >> >> We had our log server process hard lock over the weekend and it >> appears >> >> that the default heap settings were too low. There were thousands and >> >> thousands of “out of heap memory” errors in the log and then it just >> stopped >> >> processing and had to be kill -9’ed. >> >> >> >> >> >> >> >> Before the setting above, our Log server was flatlined at 5G memory >> usage. >> >> 90% of that was graylog. Now it’s at 9.5G or so. I just hope this is >> enough. >> >> We’re currently getting about 1100 messages/sec and that number will >> >> increase in the future. >> > >> > -- >> > 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/groups/opt_out. >> > >> > >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/2cf10bf8-b4ce-4717-b67c-656dc78014a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
