Hi Roberto, I'm sure you think your issue is urgent, but please stick to one thread on the mailing list for each individual problem:
- https://groups.google.com/d/msg/graylog2/tw9IH9uw_l4/B68bwV6NAgAJ - https://groups.google.com/d/msg/graylog2/Yz3jmpfqnwQ/0jEowgPqAgAJ Cheers, Jochen On Tuesday, 26 July 2016 20:59:39 UTC+2, [email protected] wrote: > > Dear, I'm using Graylog 1.3 with CPU x 10, RAM x 40GB and HD x 1.5 TB. > > The input is about 4500 logs/second. > > Today I have received this warning: > > Journal utilization is too hig > Journal utilization is too high and may go over the limit soon. Please > verify that your Elasticsearch cluster is healthy and fast enough. You may > also want to review your Graylog journal settings and set a higher limit. > (Node: *ea2b7f43-cce0-4288-b344-a4e748e3c372*, journal utilization: 96.0%) > > and now the journal has 12 millons of logs (in disk). > > I've increased the heap size to 16 GB: > > /etc/default/elasticsearch: > > ES_HEAP_SIZE=16g > > and I've done this: > > /etc/default/graylog-server: > > GRAYLOG_SERVER_JAVA_OPTS="-Xms16g -Xmx20g -XX:NewRatio=1 -XX:PermSize=256m > -XX:MaxPermSize=512m -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC > -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC > -XX:-OmitStackTraceInFastThrow" > > How can I solve this journal problem please??? > > Thanks a lot, > > > Roberto > -- 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/dd097d8f-5159-4bf5-b5d7-ba8117af49f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
