We are reaching resource capacity on the single graylog-server we have. Currently I have one machine running mongodb and graylog-server and another server running ES. This has been working like a charm, but I am now hitting CPU starvation on the graylog-servers two or three times a day during heavy usage.
I am trying to add another Graylog-server into the mix, but running into issues - I am using puppet to deploy everything. I set mongodb on graylog-server1 to listen to the IP rather than localhost and have graylog-server look at that IP. When I deploy graylog-server2, I set mongodb destination to be the IP of graylog-server1 and set the appropraite unicast address for ES. What this achives, is it duplicates the graylog-server1 node, mimicking the rate of flow thorough the JVM exactly. So for some reason the second node joins as an exact copy of the first one - both shows up as the same node name as well. Any tips as to where I can investigate further? -- 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/d30e1370-4ad8-4a33-aea9-bd045f72c1a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
