[
https://issues.apache.org/jira/browse/KAFKA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634292#comment-13634292
]
Jun Rao commented on KAFKA-864:
-------------------------------
If we just want to use a new broker to replace a failed one, a simpler solution
is to just set the broker.id of the new broker to be the same as the failed
one. When you restart the new broker, it will automatically replicate all
missing data. No need to run the partition reassignment tool.
> bin/kafka-gen-reassignment.sh
> -----------------------------
>
> Key: KAFKA-864
> URL: https://issues.apache.org/jira/browse/KAFKA-864
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.8
> Reporter: Scott Clasen
>
> Better tooling for replacing failed brokers and reassigning partitions.
> The output of ./bin/kafka-list-topic.sh makes doing this in bulk painful.
> Tool should output json format acceptable to
> ./bin/kafka-reassign-partitions.sh
> Spec: bin/kafka-gen-reassignment.sh
> Option Description
> ------ -----------
> --topic <topic> REQUIRED: The topic to be reassigned.
> Defaults to all existing topics.
> (default: )
> --partition <partition> REQUIRED: The partition to be
> reassigned.
> Defaults to all partitions.
> (default: )
> --from <broker-id> REQUIRED: The broker to reassign the
> partition from
> --to <broker-id> REQUIRED: The broker to reassign the
> partition to.
> --zookeeper <urls> REQUIRED: The connection string for
> the zookeeper connection in the form
> host:port. Multiple URLS can be
> given to allow fail-over.
> Workflow: Replacing a broker
> ./bin/kafka-gen-reassignment.sh --zookeeper <zks> --from <failed> --to
> <new> > reassign.json
> ./bin/kafka-reassign-partitions.sh --zookeeper <zks> --path-to-json-file
> reassign.json
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
