Re: spam of [kafka-processor-9092-0] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4.

2014-06-11 Thread François Langelier
Thank Joel, I try to put the trace but I saw nothing... maybe I did it wrong... anyway, I tried another way... I started the console consumer and producer on a new topic to my remote brokers... The topic was create successfully but when i produce a message, nothing happen... - The message

Re: spam of [kafka-processor-9092-0] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4.

2014-06-11 Thread François Langelier
FYI, I found out what was wrong and I think it's a wierd behaviour that you guys may want to fix... First of all, my setup is the following I have 3 brokers named : kaf1.kafka.mydns - 50.50.50.51 kaf2.kafka.mydns - 50.50.50.52 kaf3.kafka.mydns - 50.50.50.53 Those are the name in the DNS.

Re: spam of [kafka-processor-9092-0] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4.

2014-06-11 Thread Jun Rao
You may want to take a look at https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whycan'tmyconsumers/producersconnecttothebrokers ? Thanks, Jun On Wed, Jun 11, 2014 at 12:12 PM, François Langelier f.langel...@gmail.com wrote: FYI, I found out what was wrong and I think it's a wierd

spam of [kafka-processor-9092-0] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4.

2014-06-10 Thread François Langelier
Hi all! I have 3 brokers and I keep getting this message: [kafka-processor-9092-0] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4. or [kafka-processor-9092-1] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4. Do anyone know what that means???

Re: spam of [kafka-processor-9092-0] INFO kafka.network.Processor - Closing socket connection to /172.23.44.4.

2014-06-10 Thread Joel Koshy
The broker logs that whenever it closes a connection to a client (e.g., if there was an error or the client decides to close its connection after talking to the broker). If you enable TRACE level on kafka.request.logger you can see precisely what requests are coming in. Joel On Tue, Jun 10,