You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "huxihx (Jira)" <ji...@apache.org> on 2019/08/30 02:15:00 UTC
[jira] [Commented] (KAFKA-8732) specifying a non-existent broker to
./bin/kafka-reassign-partitions.sh leads to reassignment never getting
completed.
[ https://issues.apache.org/jira/browse/KAFKA-8732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919121#comment-16919121 ]
huxihx commented on KAFKA-8732:
-------------------------------
The issue was already fixed in newer versions where ReassignPartitionsCommand checks existence for to-be-reassigned brokers before the execution.
> specifying a non-existent broker to ./bin/kafka-reassign-partitions.sh leads to reassignment never getting completed.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-8732
> URL: https://issues.apache.org/jira/browse/KAFKA-8732
> Project: Kafka
> Issue Type: Bug
> Components: controller, tools
> Affects Versions: 0.10.1.1
> Environment: Ubuntu-VERSION="14.04.5 LTS"
> Reporter: Ron1994
> Priority: Critical
> Labels: bin, tools
>
> Specifying a non-existent broker to ./bin/kafka-reassign-partitions.sh leads to reassignment never getting completed.
> My reassignment is getting struck if I provide non-existing broker ID. My kafka version is 0.10.1.1.
>
>
> {code:java}
> ./kafka-reassign-partitions.sh --zookeeper zk:2181 --reassignment-json-file le.json --execute
> Current partition replica assignment
> {"version":1,"partitions":[{"topic":"cv-topic","partition":0,"replicas":[1011131,101067,98,101240]}]}
> Save this to use as the --reassignment-json-file option during rollback
> Successfully started reassignment of partitions.
> {code}
> In this 98 is the non-existing broker. Deleting reassign_partitions znode is of no use as well. As when I describe the same topic the 98 broker is out of sync.
>
>
> {code:java}
> Topic:cv-topic PartitionCount:1 ReplicationFactor:4 Configs:
> Topic: cv-topic Partition: 0 Leader: 1011131 Replicas: 1011131,101067,98,101240 Isr: 1011131,101067,101240
> {code}
> Now 98 will always be out of sync.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)