Did you ever find a solution to this? I am having the same issue on a graylog 2.0 server.
On Monday, May 2, 2016 at 5:03:48 AM UTC-4, [email protected] wrote: > > And I also upgraded to graylog 2.0GA > > Le lundi 2 mai 2016 11:01:10 UTC+2, [email protected] a écrit : >> >> I've just upgraded the ram and cpu of all the nodes but I still got the >> same issue. Process and output buffers are at 100% and the journal keeps on >> filling. >> Here is the new configuration: >> graylog server with 9 vcpu and 8 gig of ram (4gig allocated to graylog) >> elasticsearch nodes with 4 vcpu and 8 gig of ram (4 gig allocated to >> elasticsearch) >> >> Is there any metrics that could help to find where the bottleneck is ? >> >> Thanks ! >> >> Le mardi 26 avril 2016 16:22:12 UTC+2, Peter Krammer a écrit : >>> >>> Based on that both the Process and the Output buffers are full, I would >>> say your elasticsearch nodes are not fast enough. >>> They seem undersized in my eyes and should have more CPU and RAM. >>> Also check if you set your -Xms and -Xmx settings (for both graylog and >>> elasticsearch) to reasonable values, it helped me alot to increase them to >>> half of my RAM size. (eg. -Xms8g -Xmx8g ) >>> >> -- 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/479c8b6d-3a3a-4727-a5c6-4fb8b03ecfc9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
