title: Kafka: Partitions reassignment not happening
body: <p>I am getting an error while migrating data between Kafka brokers.</p>
  
  <p>I am using kafka-reassignment tool to reassign partitions to a different broker without any throttling(because it didn't worked with the below command.). There were around 400 partitions of 50 topics.</p>
  
  <pre><code>Apache Kafka 1.1.0
  Confluent Docker Image tag : 4.1.0
  </code></pre>
  
  <p>Command:</p>
  
  <pre><code>kafka-reassign-partitions --zookeeper IP:2181  --reassignment-json-file proposed.json --execute —throttle 100000000
  </code></pre>
  
  <p>After some time, I am able to see the below error continuously on the target broker.</p>
  
  <pre><code>[2019-09-21 11:24:07,625] INFO [ReplicaFetcher replicaId=4, leaderId=0, fetcherId=0] Error sending fetch request (sessionId=514675011, epoch=INITIAL) to node 0: java.io.IOException: Connection to 0 was disconnected before the response was read. (org.apache.kafka.clients.FetchSessionHandler)
  
  [2019-09-21 11:24:07,626] WARN [ReplicaFetcher replicaId=4, leaderId=0, fetcherId=0] Error in response for fetch request (type=FetchRequest, replicaId=4, maxWait=500, minBytes=1, maxBytes=10485760, fetchData={TOPIC-4=(offset=4624271, logStartOffset=4624271, maxBytes=104
  8576), TOPIC-2=(offset=1704819, logStartOffset=1704819, maxBytes=1048576), TOPIC-8=(offset=990485, logStartOffset=990485, maxBytes=1048576), TOPIC-1=(offset=1696764, logStartOffset=1696764, maxBytes=1048576), TOPIC-7=(offset=991507, logStartOffset=991507, maxBytes=10485
  76), TOPIC-5=(offset=988660, logStartOffset=988660, maxBytes=1048576)}, isolationLevel=READ_UNCOMMITTED, toForget=, metadata=(sessionId=514675011, epoch=INITIAL)) (kafka.server.ReplicaFetcherThread)
  
  java.io.IOException: Connection to 0 was disconnected before the response was read
      at org.apache.kafka.clients.NetworkClientUtils.sendAndReceive(NetworkClientUtils.java:97)
      at kafka.server.ReplicaFetcherBlockingSend.sendRequest(ReplicaFetcherBlockingSend.scala:96)
      at kafka.server.ReplicaFetcherThread.fetch(ReplicaFetcherThread.scala:220)
      at kafka.server.ReplicaFetcherThread.fetch(ReplicaFetcherThread.scala:43)
      at kafka.server.AbstractFetcherThread.processFetchRequest(AbstractFetcherThread.scala:146)
      at kafka.server.AbstractFetcherThread.doWork(AbstractFetcherThread.scala:111)
      at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:82)
  </code></pre>
  
  <p>Zookeeper status:</p>
  
  <pre><code> ls /admin/reassign_partitions
  []
  </code></pre>
  
  <p>I am using <code>t2.medium</code> type EC2 instances and gp2 type EBS volumes with 120GB size.</p>
  
  <p>I am able to connect to the zookeeper from all brokers.</p>
  
  <p><code>[zk: localhost:2181(CONNECTED) 3] ls /brokers/ids [0, 1, 2, 3]</code></p>
  
  <p>I am using IP address for all brokers, so DNS mismatch is also not the case.</p>
  
  <p>Also, I am not able to see any topic scheduled for reassignment in zookeeper.</p>
  
  <pre><code>[zk: localhost:2181(CONNECTED) 2] ls /admin/reassign_partitions
  []
  </code></pre>
  
  <p>Interestingly, I can see data is pilling up for the partitions which are not listed above. But the partitions listed in the error are not getting migrated as of now.</p>
  
  <p>I am using confluent kafka docker image.</p>
  
  <p>Kafka Broker Setting:
  <a href="https://gist.github.com/ethicalmohit/cd44f580356ca02250760a307d90b54d" rel="nofollow noreferrer">https://gist.github.com/ethicalmohit/cd44f580356ca02250760a307d90b54d</a></p>