Still flailing without guidance I have some more questions. I changed elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300, and with 9300 it appears that the default index (node) is being filled. Graylog creates a second node that I don't believe I need (port 9350 which I didn't set or chose), but if I look at the elasticsearch parameters after adjusting heap size in sysconfig, Graylog "Nodes" is showing me the heap size for the index that isn't being used (the one set in /etc/sysconfig/graylog-server). The memory usage fluctuates as though something is happening, but that index is totally empty. The default dynamically named index is filling, and I have increased the heap size there in /etc/sysconfig/elasticsearch. So the web interface is showing me status on the unused index (node).
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. > > From the beginning I have wondered why I need the default elastic index > (node with the dynamic naming) that never seems to be used, as well as the > graylog index(node). > > The default elastic index seems to have all of the recommended tweaks > (like mlockall), but the graylog index doesn't. Where exactly am I supposed > to be changing them? > > -- 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.
