Hello Matt, Are you by any chance running inputs that have the force_rdns flag set?
---HenrikJ On 2. jun. 2015 kl. 17.37.16 CEST, Matt Hines <[email protected]> wrote:Hey guys, We've just updated our Graylog setup by moving the ES to another box to give it space to breathe. But now we're seeing a large increase in msg/s coming into the graylog-server, at peak times, between 600-1200. This amount is only going to get bigger as users increase. My issue is, when the number breaches the 600 msgs/s number, graylog starts to struggle and starts filling up its process buffer and the CPU ramps up to 100% and stays there until the peak period is over and it has cleared the buffer out. The box is an AWS box, 2CPU, 8GB RAM. I have no idea if this hardware should be enough for this number of messages? If so, is there some tweaking I can do to optimise the system? If not, what would you recommend, I know it's mainly CPU based but would it be best to cluster a second box, or increase this box? Also, at what point will I start to lose messages incoming? When the process buffer and journal are both full? We're running Graylog v1.0.2 Thanks for any help! -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
