Hi Jochen, of that I am aware, alas, a SAN usually provides storage for a virtual infrastructure and as such acts as a "local" drive :)
I´ve been trying to find the right settings for our environment for the last 2 days (amount of procs in the server.conf, output_batch_size, etc.) in order to get our 1.3.4 to perform better but still having considerable issues with it. Which might be due to a very extensive GROK-pattern input which seems to cost a lot of CPU cycles. One thing I noticed though, as soon as the input buffer is full (happens after proccess buffer filled up) graylog 1.3.4 seems to "die". Symptoms as such are: -incoming messages are dropped (due to input buffer being full. my guess) -Buffer will never be emptied again until you restart the graylog service -At times input/output reverts to 0 and CPU cycles idle Maybe if I threw even more CPUs at my graylog VM it might solve some issues, don´t know yet. OR I´ll need to get rid of costly GROK-Patterns (which are needed for the terrible log-structure of the sidewinder firewall). Am Dienstag, 3. Januar 2017 12:09:04 UTC+1 schrieb Jochen Schalanda: > > Hi Jerri, > > the Graylog disk journal should *always* run locally and *never* be > placed on a "remote" disk (like a SAN or any other network storage). > > You can change the journal directory with the message_journal_dir > <https://github.com/Graylog2/graylog2-server/blob/2.1.2/misc/graylog.conf#L376-L383> > > setting. > > Cheers, > Jochen > > On Tuesday, 3 January 2017 11:59:47 UTC+1, Jerri Son wrote: >> >> Just to share my finding after testing a lot: once I disabled the >> intranel graylog journaling I get the desired I/O. This might be attributed >> to my SAN backend but surely enough >> I can finally run the latest and greatest gralyog features :) >> > -- 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/28b11ebe-ce42-4518-bc7f-2624c19f6786%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
