title: aborting kafka reassign partition action
body: <p>I'm using kafka 0.8.2 &amp; one of my kafka servers died (no way to recover the data on the disks). There is a topic, with replication of 1, with one of the partitions on the dead server. I thought a reassignment would move the metadata for that partition to a new server without needing the data, but the reassignment is stuck to <code>in progress</code>.</p>
  
  <p>I ran:</p>
  
  <pre><code>$ /opt/kafka/kafka/bin/kafka-reassign-partitions.sh --zookeeper myzookeeper.my.com --reassignment-json-file new_assignment.json --verify
  Status of partition reassignment:
  Reassignment of partition [topicX,1] is still in progress
  </code></pre>
  
  <p>This will never succeed since the dead server is never coming back.</p>
  
  <p>In the new server's log, I saw:</p>
  
  <pre><code>[2015-05-28 06:25:15,401] INFO Completed load of log topicX-1 with log end offset 0 (kafka.log.Log)
  [2015-05-28 06:25:15,402] INFO Created log for partition [topicX,1] in /mnt2/data/kafka with properties {segment.index.bytes -&gt; 10485760, file.delete.delay.ms -&gt; 60000, segment.bytes -&gt; 536870912, flush.ms -&gt; 9223372036854775807, delete.retention.ms -&gt; 86400000, index.interval.bytes -&gt; 4096, retention.bytes -&gt; -1, min.insync.replicas -&gt; 1, cleanup.policy -&gt; delete, unclean.leader.election.enable -&gt; true, segment.ms -&gt; 604800000, max.message.bytes -&gt; 1000012, flush.messages -&gt; 9223372036854775807, min.cleanable.dirty.ratio -&gt; 0.5, retention.ms -&gt; 259200000, segment.jitter.ms -&gt; 0}. (kafka.log.LogManager)
  [2015-05-28 06:25:15,403] WARN Partition [topicX,1] on broker 4151132: No checkpointed highwatermark is found for partition [topicX,1] (kafka.cluster.Partition)
  [2015-05-28 06:25:15,405] INFO [ReplicaFetcherManager on broker 4151132] Removed fetcher for partitions  (kafka.server.ReplicaFetcherManager)
  [2015-05-28 06:25:15,408] INFO [ReplicaFetcherManager on broker 4151132] Added fetcher for partitions List() (kafka.server.ReplicaFetcherManager)
  [2015-05-28 06:25:15,411] INFO [ReplicaFetcherManager on broker 4151132] Removed fetcher for partitions  (kafka.server.ReplicaFetcherManager)
  [2015-05-28 06:25:15,413] INFO [ReplicaFetcherManager on broker 4151132] Added fetcher for partitions List() (kafka.server.ReplicaFetcherManager)
  </code></pre>
  
  <p>Is there a way to force it to complete or abort the reassignment action?</p>