This should be just a message fetch failure. The socket was disconnected when broker was writing to it. There should not be data loss.
Jiangjie (Becket) Qin On 5/27/15, 11:00 AM, "Andrey Yegorov" <andrey.yego...@gmail.com> wrote: >I've noticed a few exceptions in the logs like the one below, does it >indicate data loss? should I worry about this? >What is the possible reason for this to happen? >I am using kafka 0.8.1.1 > >ERROR Closing socket for /xx.xxx.xxx.xxx because of error >(kafka.network.Processor) > >kafka.common.KafkaException: Size of FileMessageSet >/data/kafka/topic-name-11/00000000000014340499.log has been truncated >during write: old size 26935, new size 0 > > at kafka.log.FileMessageSet.writeTo(FileMessageSet.scala:144) > > at kafka.api.PartitionDataSend.writeTo(FetchResponse.scala:69) > > at kafka.network.MultiSend.writeTo(Transmission.scala:102) > > at kafka.api.TopicDataSend.writeTo(FetchResponse.scala:124) > > at kafka.network.MultiSend.writeTo(Transmission.scala:102) > > at kafka.api.FetchResponseSend.writeTo(FetchResponse.scala:219) > > at kafka.network.Processor.write(SocketServer.scala:375) > > at kafka.network.Processor.run(SocketServer.scala:247) > > at java.lang.Thread.run(Thread.java:745) > >---------- >Andrey Yegorov
