kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Neha Narkhede <neha.narkh...@gmail.com>
Subject Re: java.io.IOException: Broken pipe
Date Fri, 15 Mar 2013 13:06:23 GMT
>From the error it seems that the server was not able to write the fetch
response on the socket since the socket was closed. Do you see any errors
on the consumer on 10.2.201.20 <http://10.2.201.202/> ? The consumer could've
closed the socket due to some error or could've died.

Thanks,
Neha

On Friday, March 15, 2013, Yonghui Zhao wrote:

> This exception happened many times in high through put in kafka 0.7.2
>
> [2013-03-15 17:27:16,691] ERROR Closing socket for /10.2.201.202 because
> of
> error (kafka.network.Processor)
> java.io.IOException: Broken pipe
>     at sun.nio.ch.FileChannelImpl.transferTo0(Native Method)
>     at
> sun.nio.ch.FileChannelImpl.transferToDirectly(FileChannelImpl.java:456)
>     at sun.nio.ch.FileChannelImpl.transferTo(FileChannelImpl.java:557)
>     at kafka.message.FileMessageSet.writeTo(FileMessageSet.scala:102)
>     at kafka.server.MessageSetSend.writeTo(MessageSetSend.scala:53)
>     at kafka.network.MultiSend.writeTo(Transmission.scala:91)
>     at kafka.network.Processor.write(SocketServer.scala:339)
>     at kafka.network.Processor.run(SocketServer.scala:216)
>     at java.lang.Thread.run(Thread.java:679)
>
>
> It seems it doesn't matter much.
>
> I want to know if we need take actions if we see this exception.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message