Hi Ariel, MongoDB shouldn't need much processing power when being used by Graylog.
Are there any error messages in the logs of your MongoDB nodes? Are there any unusually large collections in the MongoDB database used by Graylog? Which MongoDB storage engine (MMAPv1, WiredTiger) are you using? Cheers, Jochen On Tuesday, 19 July 2016 21:09:47 UTC+2, Ariel Godinez wrote: > > Hello, > > I am running the single node setup below: > > Graylog 2.0.3 > MongoDB 3.2.7 > Elasticsearch 2.3.3 > Red Hat Enterprise Linux Server 6.5 > Java 8 > NXlog and Graylog Collector Sidecar for reading from local logs > > On average graylog is reading about 50 logs per second. MongoDB is not > being used for any other services other than graylog. Yet, occasionally I > notice that the system is hanging and proceed to do a *$top *where I see > that the mongod process is consuming well over 100% CPU. I'm wondering if > the load is just to heavy or if there is something wrong with my setup that > is causing mongod to overload. > > I am not seeing any warnings or errors in the graylog server logs or in > the mongod.log file when I look after a slowdown has occurred. Any advice > on how to further investigate would be much appreciated. > > Thanks, > Ari > > > -- 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/49af2e8a-a179-466a-ac9c-79682d1fcbf2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
