You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "huxi (JIRA)" <ji...@apache.org> on 2017/05/03 01:49:05 UTC

[jira] [Assigned] (KAFKA-5161) reassign-partitions to check if broker of ID exists in cluster

     [ https://issues.apache.org/jira/browse/KAFKA-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

huxi reassigned KAFKA-5161:
---------------------------

    Assignee: huxi

> 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
>
> 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)