Sure. Thanks Neha. Created Issue:
https://issues.apache.org/jira/browse/KAFKA-1041
On Wed, Sep 4, 2013 at 10:32 AM, Neha Narkhede wrote:
> Ideally if the producer runs into any error, it should close the previous
> socket and open a new one. Seems like that is not happening here. I will
> tak
Ideally if the producer runs into any error, it should close the previous
socket and open a new one. Seems like that is not happening here. I will
take a closer look at this today. Do you mind filing a bug?
Thanks,
Neha
On Sep 4, 2013 7:23 AM, "Rajasekar Elango" wrote:
> I can easily reproduce t
I can easily reproduce this with console producer, If I run console
producer with right hostname and if broker is not running, the console
producer will exit after three tries. But If I run console producer with
unresolvable broker, it throws below exception and continues to wait for
user input, e
Interesting. What errors/exceptions do you see in the producer logs?
Thanks,
Neha
On Tue, Sep 3, 2013 at 3:28 PM, Rajasekar Elango wrote:
> We found a issue that if broker host is un resolvable, the number of file
> handle keep increasing for every message we produce and eventually it uses
> up
We found a issue that if broker host is un resolvable, the number of file
handle keep increasing for every message we produce and eventually it uses
up all available files handles in operating system. If broker itself is not
running and broker host name is resolvable, open file handles count stays
