I bumped the memory to 4G for Xms and Xms. It doesn't quite solve the problem with the warnings, but seems to reduce the frequency of it happening. Logging is indeed more consistent, but none the less the errors are still occurring.
2016-11-09 10:01:55,121 WARN : org.graylog2.periodical.NodePingThread - Did not find meta info of this node. Re-registering. 2016-11-09 10:09:59,343 WARN : org.graylog2.periodical.NodePingThread - Did not find meta info of this node. Re-registering. I also noticed in the server overview, these entries also coincide with the server log warnings. 2016-11-09T10:09:59-08:00 61c41b59 / log-input1.blah.com <https://log-viewer.docmagic.com/system/nodes/61c41b59-6430-491a-8873-ea62e679d8b8> Notification condition [NO_MASTER] has been fixed. 2016-11-09T10:09:27-08:00 61c41b59 / log-input1.blah.com <https://log-viewer.docmagic.com/system/nodes/61c41b59-6430-491a-8873-ea62e679d8b8> SystemJob <62391970-a6a6-11e6-bfb4-0050568f1eb6> [org.graylog2.indexer. indices.jobs.OptimizeIndexJob] finished in 545183ms. 2016-11-09T10:01:55-08:00 61c41b59 / log-input1.blah.com <https://log-viewer.docmagic.com/system/nodes/61c41b59-6430-491a-8873-ea62e679d8b8> Notification condition [NO_MASTER] has been fixed. 2016-11-09T10:00:22-08:00 61c41b59 / log-input1.blah.com <https://log-viewer.docmagic.com/system/nodes/61c41b59-6430-491a-8873-ea62e679d8b8> SystemJob <4ef156d3-a6a6-11e6-bfb4-0050568f1eb6> [org.graylog2.indexer. indices.jobs.SetIndexReadOnlyAndCalculateRangeJob] finished in 2792ms. 2016-11-09T10:00:22-08:00 61c41b59 / log-input1.blah.com <https://log-viewer.docmagic.com/system/nodes/61c41b59-6430-491a-8873-ea62e679d8b8> Optimizing index <graylog_3691>. 2016-11-09T10:00:22-08:00 61c41b59 / log-input1.blah.com <https://log-viewer.docmagic.com/system/nodes/61c41b59-6430-491a-8873-ea62e679d8b8> Flushed and set <graylog_3691> to read-only. It seems like the index optimization task may be related to the problem? This also still do not give any means to troubleshoot the source messages of the errors in the server logs. On Wednesday, November 9, 2016 at 5:23:42 AM UTC-8, Jochen Schalanda wrote: > > Hi Jimmy, > > On Wednesday, 9 November 2016 11:00:13 UTC+1, Jimmy Chen wrote: >> >> Graylog is on 2.1.2 which was just updated yesterday. ElasticSearch is >> 2.3.5. >> The Graylog server is running as a VM with 8 cores, 4G of RAM, 1G >> assigned to heap. We have the web front end running on another VM and >> connected as Graylog slave. >> > > 1 GiB of heap memory is too little to run a productive instance of > Graylog. Try providing at least 2 GiB of memory for the Graylog process. > > Cheers, > Jochen > -- 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/c3df1b68-e961-47db-acef-7062d65ab1f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
