I saw this recently as well. This could result from either really long GC pauses or slow Zookeeper responses. The former can result from too big of a memory heap or sub-optimal GC algorithm/GC configuration.
--John On Tue, Jul 18, 2017 at 3:18 AM, Mackey star <mackeys...@hotmail.com> wrote: > [2017-07-15 08:45:19,071] WARN [ReplicaFetcherThread-0-3], Error in fetch > kafka.server.ReplicaFetcherThread$FetchRequest@60192273 (kafka.server. > ReplicaFetcherThread) > java.io.IOException: Connection to 3 was disconnected before the response > was read > at kafka.utils.NetworkClientBlockingOps$$anonfun$blockingSendAndReceive$ > extension$1$$anonfun$apply$1.apply(NetworkClientBlockingOps.scala:115) > at kafka.utils.NetworkClientBlockingOps$$anonfun$blockingSendAndReceive$ > extension$1$$anonfun$apply$1.apply(NetworkClientBlockingOps.scala:112) > at scala.Option.foreach(Option.scala:236) > at kafka.utils.NetworkClientBlockingOps$$anonfun$blockingSendAndReceive$ > extension$1.apply(NetworkClientBlockingOps.scala:112) > at kafka.utils.NetworkClientBlockingOps$$anonfun$blockingSendAndReceive$ > extension$1.apply(NetworkClientBlockingOps.scala:108) > at kafka.utils.NetworkClientBlockingOps$.recursivePoll$1( > NetworkClientBlockingOps.scala:137) > at kafka.utils.NetworkClientBlockingOps$.kafka$utils$ > NetworkClientBlockingOps$$pollContinuously$extension( > NetworkClientBlockingOps.scala:143) > at kafka.utils.NetworkClientBlockingOps$.blockingSendAndReceive$extension( > NetworkClientBlockingOps.scala:108) > at kafka.server.ReplicaFetcherThread.sendRequest( > ReplicaFetcherThread.scala:253) > at kafka.server.ReplicaFetcherThread.fetch(ReplicaFetcherThread.scala:238) > at kafka.server.ReplicaFetcherThread.fetch(ReplicaFetcherThread.scala:42) > at kafka.server.AbstractFetcherThread.processFetchRequest( > AbstractFetcherThread.scala:118) > at kafka.server.AbstractFetcherThread.doWork(AbstractFetcherThread.scala: > 103) > at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:63) > >
