On 06/20/2016 05:28 AM, Avi Asulin wrote:
Hi
We are using kafka 0.8.2 with scala 2.10 version
We currently have 3 brokers and we are working with ~ 170 producers
We frequently get the Error
ERROR Closing socket for /170.144.181.50 because of error
(kafka.network.Processor)
java.io.IOException: C
Hi
We are using kafka 0.8.2 with scala 2.10 version
We currently have 3 brokers and we are working with ~ 170 producers
We frequently get the Error
ERROR Closing socket for /170.144.181.50 because of error
(kafka.network.Processor)
java.io.IOException: Connection reset by peer
at sun.nio.c
Hi Even, and Jay,
I am not saying this is logging issue (logging is absolutely needed and can
not turn off ERROR or WARN level in any env). What I am saying is there is
TCP connection is establish and leaked till other side close it or producer
is close or JVM exits.
Imagine you have l"TCP Routi
Agree with Jay. It's unfortunate that this gets logged because in this case
it's just noise, but this is an exception that can happen both in
potentially bad cases (remote peer closed connection forcibly with
outstanding unprocessed data) or in normal cases that aren't problematic
(TCP connection t
I don't think this is a bug. Currently we don't support timing out
connections in the clients, which would be a good feature to add. As a
result the connection remains until the LB kills it. When that happens you
get a message logged that the connection was unexpectedly closed, which I
think is wha
HI Ewen,
The root of the problem is leak of TCP connection which idle for while. It
is just a log message as you mentioned, but suppose you have 50 or more
producer instances created by application and everyone of then will print
above log that becomes little concern.
We configured producer wit
Bhavesh,
I'm unclear what the impact is here. The line numbers don't match up
exactly with trunk or 0.8.2.0, but it looks like this exception is just
caught and logged. As far as I can tell the producer would continue to
function normally. Does this have any impact on the producer or is the
concer
HI Kafka Team,
Please confirm if you would like to open Jira issue to track this ?
Thanks,
Bhavesh
On Mon, Feb 9, 2015 at 12:39 PM, Bhavesh Mistry
wrote:
> Hi Kakfa Team,
>
> We are getting this connection reset by pears after couple of minute aster
> start-up of producer due to infrastructur
Hi Kakfa Team,
We are getting this connection reset by pears after couple of minute aster
start-up of producer due to infrastructure deployment strategies we have
adopted from LinkedIn.
We have LB hostname and port as seed server, and all producers are getting
following exception because of TCP i
