Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> java.io.IOException: Broken pipe


Copy link to this message
-
Re: java.io.IOException: Broken pipe
Modify the log4j properties for senseidb and set kafka.consumer to INFO.
you can check the senseidb startup scripts on how they configure their
log4j.

Thanks,
Neha

On Tuesday, March 19, 2013, Yonghui Zhao wrote:

> Hi Neha,
>
> How can I enable all kafka consumer log in senseidb?
> Btw: I am using kafka 0.7.2 java client.
>
> 2013/3/19 Neha Narkhede <[EMAIL PROTECTED] <javascript:;>>
>
> > The logs show that senseidb is prematurely closing the socket connection
> to
> > the Kafka broker. I would enable atleast INFLO logging for Kafka in
> > Senseidb to see what the issue is.
> >
> > Thanks,
> > Neha
> >
> > On Monday, March 18, 2013, Yonghui Zhao wrote:
> >
> > > Thanks Neha,
> > >
> > > I use one kafka server with 4 partitions and 3 consumers(senseidb).
> > >
> > > Kafka server producer input rate is about 10k.
> > > And each consumer consuming rate is about 3k.
> > >
> > > I see this exceptions many times, kafka has this exception on each
> > > consumers, but I didn't find error log in consumer side,
> > consumer(senseidb)
> > > is alive all the time.
> > > Is it possible the exception is related with high input/output rate?
> > >
> > > And some times another exception(*Connection reset by peer*) happened.
> > >
> > > [2013-03-18 21:18:29,107] ERROR Closing socket for /10.2.201.203because
> > > of error (kafka.network.Processor)
> > > java.io.IOException: Connection reset by peer
> > >     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)
> > >
> > >
> > >
> > > Btw: the log is full of "*Closing socket connection*", is it normal?
> > >
> > > From the code each "Closing" log should  correspond to one exception
> > >
> > > In SocketServer.scala:
> > >
> > > *catch {**
> > > **            case e: EOFException => {**
> > > **              logger.info("Closing socket connection to
> > > %s.".format(channelFor(key).**socket.getInetAddress))**
> > > **              close(key)**
> > > **        }**
> > > *
> > >
> > > [2013-03-18 21:28:42,791] INFO *Closing socket connection* to /
> > > 10.2.201.201. (kafka.network.Processor)
> > > [2013-03-18 21:28:43,954] INFO *Closing socket connection* to /
> > > 10.2.201.201. (kafka.network.Processor)
> > > [2013-03-18 21:28:45,322] INFO *Closing socket connection* to /
> > > 10.2.201.201. (kafka.network.Processor)
> > > [2013-03-18 21:28:47,045] INFO *Closing socket connection *to /
> > > 10.2.201.201. (kafka.network.Processor)
> > > [2013-03-18 21:28:50,110] ERROR Closing socket for /10.2.201.201because
> > > 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)
> > >
> > >
> > >
> > > 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