[
https://issues.apache.org/jira/browse/KAFKA-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-5161.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.11.0.0
Issue resolved by pull request 2962
[https://github.com/apache/kafka/pull/2962]
> reassign-partitions to check if broker of ID exists in cluster
> --------------------------------------------------------------
>
> Key: KAFKA-5161
> URL: https://issues.apache.org/jira/browse/KAFKA-5161
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.10.1.1
> Environment: Debian 8
> Reporter: Lawrence Weikum
> Assignee: huxi
> Priority: Minor
> Fix For: 0.11.0.0
>
>
> A topic was created with only one replica. We wanted to increase it later to
> 3 replicas. A JSON file was created, but the IDs for the brokers were
> incorrect and not part of the system.
> The script or the brokers receiving the reassignment command should first
> check if the new IDs exist in the cluster first and then continue, throwing
> an error to the user if there is one that doesn't.
> The current effect of assign partitions to non-existant brokers is a stuck
> replication assignment with no way to stop it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
