You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/01/17 13:12:26 UTC
[jira] [Updated] (KAFKA-1300) Added WaitForReplaction admin tool.
[ https://issues.apache.org/jira/browse/KAFKA-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-1300:
-------------------------------
Fix Version/s: (was: 0.10.2.0)
> Added WaitForReplaction admin tool.
> -----------------------------------
>
> Key: KAFKA-1300
> URL: https://issues.apache.org/jira/browse/KAFKA-1300
> Project: Kafka
> Issue Type: New Feature
> Components: tools
> Affects Versions: 0.8.0
> Environment: Ubuntu 12.04
> Reporter: Brenden Matthews
> Labels: patch
> Attachments: 0001-Added-WaitForReplaction-admin-tool.patch
>
>
> I have created a tool similar to the broker shutdown tool for doing rolling restarts of Kafka clusters.
> The tool watches the max replica lag of the specified broker, and waits until the lag drops to 0 before exiting.
> To do a rolling restart, here's the process we use:
> for (broker <- brokers) {
> run shutdown tool for broker
> terminate broker
> start new broker
> run wait for replication tool on new broker
> }
> Here's an example command line use:
> ./kafka-run-class.sh kafka.admin.WaitForReplication --zookeeper zk.host.com:2181 --num.retries 100 --retry.interval.ms 60000 --broker 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)