Edoardo Comar created KAFKA-5200:
------------------------------------
Summary: Deleting topic when one broker is down will prevent topic
to be re-creatable
Key: KAFKA-5200
URL: https://issues.apache.org/jira/browse/KAFKA-5200
Project: Kafka
Issue Type: Improvement
Components: core
Reporter: Edoardo Comar
In a cluster with 5 broker, replication factor=3, min in sync=2,
one broker went down
A user's app remained of course unaware of that and deleted a topic that
(unknowingly) had a replica on the dead broker.
The topic went in 'pending delete' mode
The user then tried to recreate the topic - which failed, so his app was left
stuck - no working topic and no ability to create one.
The reassignment tool fails to move the replica out of the dead broker -
specifically because the broker with the partition replica to move is dead :-)
Incidentally the confluent-rebalancer docs say
http://docs.confluent.io/current/kafka/post-deployment.html#scaling-the-cluster
> Supports moving partitions away from dead brokers
It'd be nice to similarly improve the opensource reassignment tool
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
