<https://lh3.googleusercontent.com/-L64niwFFD6U/V-qVNBToQOI/AAAAAAAAHJI/11u1Ex7U-H4UFjHZY4chjvoEujBDecmkgCLcB/s1600/buffers.PNG>
As you can see in the screenshot from this morning, Process and Output are full and Journal keeps growing accordingly. So process is when be when message is actually parsed and output is when sent to ES for indexing? I don't get why it would be so slow when spiking during the night however. Would need to find out what are those messages taking so long to process and index I guess. On Tuesday, 27 September 2016 11:39:12 UTC-4, Jochen Schalanda wrote: > > Hi, > > On Tuesday, 27 September 2016 16:50:44 UTC+2, [email protected] wrote: >> >> Thanks for the links but ins't the problem with the Kafka journal more >> then ES indexing really? And isn't lowering processors an issue considering >> the bottleneck? >> > > the disk journal is rarely the problem. Check your input/process/output > buffers to find out, which step in message processing is slow (hint: it's > the one with the most utilized buffer). > > 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/6c1d632e-771d-4743-a819-37806a5e4599%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
