This is an automated email from the ASF dual-hosted git repository.
jgus pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/trunk by this push:
new e426247 MINOR: Fix command examples in kafka-reassign-partitions.sh
docs (#7583)
e426247 is described below
commit e4262471c9aee4a4c04dd04ebbdbdba7e3c5ead1
Author: Mickael Maison <[email protected]>
AuthorDate: Sat Oct 26 21:16:26 2019 +0100
MINOR: Fix command examples in kafka-reassign-partitions.sh docs (#7583)
Reviewers: Jason Gustafson <[email protected]>
---
docs/ops.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/ops.html b/docs/ops.html
index 5cb1f65..0cd20bf 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -453,7 +453,7 @@
There are two interfaces that can be used to engage a throttle. The
simplest, and safest, is to apply a throttle when invoking the
kafka-reassign-partitions.sh, but kafka-configs.sh can also be used to view and
alter the throttle values directly.
<p></p>
So for example, if you were to execute a rebalance, with the below command,
it would move partitions at no more than 50MB/s.
- <pre class="brush: bash;">$ bin/kafka-reassign-partitions.sh --zookeeper
localhost:2181 --execute --reassignment-json-file bigger-cluster.json —throttle
50000000</pre>
+ <pre class="brush: bash;">$ bin/kafka-reassign-partitions.sh --zookeeper
localhost:2181 --execute --reassignment-json-file bigger-cluster.json
--throttle 50000000</pre>
When you execute this script you will see the throttle engage:
<pre class="brush: bash;">
The throttle limit was set to 50000000 B/s
@@ -526,8 +526,8 @@
<p>Some care should be taken when using throttled replication. In
particular:</p>
<p><i>(1) Throttle Removal:</i></p>
- The throttle should be removed in a timely manner once reassignment
completes (by running kafka-reassign-partitions
- —verify).
+ The throttle should be removed in a timely manner once reassignment
completes (by running kafka-reassign-partitions.sh
+ --verify).
<p><i>(2) Ensuring Progress:</i></p>
<p>If the throttle is set too low, in comparison to the incoming write rate,
it is possible for replication to not
