From ca3271e0f3e3c31cce413668c6a1ed2dacab91fe Mon Sep 17 00:00:00 2001
From: Luke Chen <showuon@gmail.com>
Date: Sun, 27 Mar 2022 15:47:24 +0800
Subject: [PATCH] MINOR: replace kafka-preferred-replica-election.sh with
 kafka-leader-election.sh (#11954)

Reviewers: Luke Chen <showuon@gmail.com>
---
 docs/ops.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ops.html b/docs/ops.html
index e5b2fb8e946..183d8acb49a 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -78,7 +78,7 @@
 
   <pre class="line-numbers"><code class="language-text">      auto.leader.rebalance.enable=true</code></pre>
     You can also set this to false, but you will then need to manually restore leadership to the restored replicas by running the command:
-  <pre class="line-numbers"><code class="language-bash">  &gt; bin/kafka-preferred-replica-election.sh --bootstrap-server broker_host:port</code></pre>
+  <pre class="line-numbers"><code class="language-bash">  &gt; bin/kafka-leader-election.sh --bootstrap-server broker_host:port --election-type preferred --all-topic-partitions</code></pre>
 
   <h4 class="anchor-heading"><a id="basic_ops_racks" class="anchor-link"></a><a href="#basic_ops_racks">Balancing Replicas Across Racks</a></h4>
   The rack awareness feature spreads replicas of the same partition across different racks. This extends the guarantees Kafka provides for broker-failure to cover rack-failure, limiting the risk of data loss should all the brokers on a rack fail at once. The feature can also be applied to other broker groupings such as availability zones in EC2.