You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "lqjacklee (Jira)" <ji...@apache.org> on 2022/04/28 17:02:00 UTC
[jira] [Created] (KAFKA-13860) add Decommissioning feature to kafka-reassign-partitions.sh
lqjacklee created KAFKA-13860:
---------------------------------
Summary: add Decommissioning feature to kafka-reassign-partitions.sh
Key: KAFKA-13860
URL: https://issues.apache.org/jira/browse/KAFKA-13860
Project: Kafka
Issue Type: Task
Reporter: lqjacklee
try to replay the issue
* 1, startup cluster with broker 1, 2
* 2, create topic a which assigned to 1 and 2
* 3, add the new broker 3 to cluster
* 4, assignment the topic a from 1,2 to 3
#
# Step 1 (generate reassignment JSON; this script):
#
# $ kafka-move-leadership.sh --broker-id 4 --first-broker-id 0 --last-broker-id 8 --zookeeper zookeeper1:2181 > partitions-to-move.json
#
# Step 2 (start reassignment process; Kafka built-in script):
#
# $ kafka-reassign-partitions.sh --zookeeper zookeeper1:2181 --reassignment-json-file partitions-to-move.json --execute
#
# Step 3 (monitor progress of reassignment process; Kafka built-in script):
#
# $ kafka-reassign-partitions.sh --zookeeper zookeeper1:2181 --reassignment-json-file partitions-to-move.json --verify
*
*
* 5,assert that no service alive in the broker 1 and 2
* 6, finally close the broker 1 and 2
--
This message was sent by Atlassian Jira
(v8.20.7#820007)