I think I temporary solved it re-creating Kafka input on Server and setting a single (1) thread.
Restarting Zookeeper server and it seems to index messages without loss.. On 06/27/2014 11:28 AM, Florent B wrote: > Hi, thank you for your answer. I did 5 jstack I send it to your e-mail. > > > On 06/27/2014 11:02 AM, Dennis Oelkers wrote: >> Hey, >> >> thanks for reporting this. Could you please take a few stack dumps and send >> it to us? >> Just calling "jstack <pid>" a few times and pipe the output to separate >> files is enough for this. >> >> Kr, >> Dennis >> >> On 27.06.2014, at 10:02, Florent B <[email protected]> wrote: >> >>> Hi, >>> >>> I have a problem with a Server that crached a few days ago. >>> >>> When I start it, it connects to Kafka server to catch up messages. But >>> after a few seconds it get stuck and 100% CPU. >>> >>> This case is not planned ? It seems that it tries to index a few hundred >>> of thousand of messages at a time, so it get stuck... >>> >>> There is no particular error in logs... >>> >>> >>> -- >>> 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. >> -- >> TORCH GmbH >> Steckelhörn 11 >> 20457 Hamburg >> Tel +49 (0)40-60945200 >> https://www.torch.sh >> >> Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175 >> Geschäftsführer: Hass Chapman, Lennart Koopmann >> -- 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.
