Re: bootstrap.servers for the new Producer

2015-08-22 Thread Kishore Senji
Thank you Ewen. This behavior is something that I'm observing. I see in the logs continuous Connect failures to the dead broker. The important thing here is I'm starting a brand new instance of the Producer after a broker is down (so no prior metadata), with that down broker also as part of the

Re: bootstrap.servers for the new Producer

2015-08-22 Thread Ewen Cheslack-Postava
You're just seeing that exception in the debugger, not the log, right? ConnectException is an IOException, so it should be caught by this block https://github.com/apache/kafka/blob/0.8.2.1/clients/src/main/java/org/apache/kafka/common/network/Selector.java#L271 , logged, and then the SelectionKey

Re: bootstrap.servers for the new Producer

2015-08-22 Thread Kishore Senji
Yes that is exactly the issue. I did not notice the close(key) is called from the poll() method as well. I was observing this even when I run my app (not in debug). I noticed it was taking 1sec (with a conditional debug) and like you mentioned the default time for reconnect.backoff.ms is 10ms and

New Async producer hangs

2015-08-22 Thread sunil kalva
Hi I am using new asyc java producer , after couple of minutes i am getting following error prio=5 os_prio=31 tid=0x7f9383685800 nid=0xea03 waiting for monitor entry [0x000123a6a000] java.lang.Thread.State: BLOCKED (on object monitor) at