You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kafka.apache.org by js...@apache.org on 2022/09/29 22:10:34 UTC
[kafka] 02/02: MINOR; Add missing code end tag (#12702)
This is an automated email from the ASF dual-hosted git repository.
jsancio pushed a commit to branch 3.3
in repository https://gitbox.apache.org/repos/asf/kafka.git
commit cdb25e10dcc45cf2fbd095dcba0a7bfe22a9d1cc
Author: José Armando García Sancio <js...@users.noreply.github.com>
AuthorDate: Thu Sep 29 15:09:00 2022 -0700
MINOR; Add missing code end tag (#12702)
Reviewers: Ismael Juma <is...@juma.me.uk>
---
docs/ops.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/ops.html b/docs/ops.html
index 9ce051316f4..470fd7e0d92 100644
--- a/docs/ops.html
+++ b/docs/ops.html
@@ -1388,7 +1388,7 @@ $ bin/kafka-acls.sh \
<pre class="line-numbers"><code class="language-bash"> > bin/kafka-storage.sh format --cluster-id uuid --config server_properties</code></pre>
- <p>It is possible for the <code>bin/kafka-storage.sh format<code> command above to fail with a message like <code>Log directory ... is already formatted<code>. This can happend when combined mode is used and only the metadata log directory was lost but not the others. In that case and only in that case, can you run the <code>kafka-storage.sh format</code> command with the <code>--ignore-formatted</code> option.</p>
+ <p>It is possible for the <code>bin/kafka-storage.sh format</code> command above to fail with a message like <code>Log directory ... is already formatted</code>. This can happend when combined mode is used and only the metadata log directory was lost but not the others. In that case and only in that case, can you run the <code>kafka-storage.sh format</code> command with the <code>--ignore-formatted</code> option.</p>
<p>Start the KRaft controller after formatting the log directories.</p>
@@ -3408,7 +3408,7 @@ for built-in state stores, currently we have:
<h5 class="anchor-heading"><a id="kraft_role" class="anchor-link"></a><a href="#kraft_role">Process Roles</a></h5>
- <p>In KRaft mode each Kafka server can be configured as a controller, a broker, or both using the <code>process.roles<code> property. This property can have the following values:</p>
+ <p>In KRaft mode each Kafka server can be configured as a controller, a broker, or both using the <code>process.roles</code> property. This property can have the following values:</p>
<ul>
<li>If <code>process.roles</code> is set to <code>broker</code>, the server acts as a broker.</li>
@@ -3438,7 +3438,7 @@ node.id=1
listeners=CONTROLLER://controller1.example.com:9093
controller.quorum.voters=1@controller1.example.com:9093,2@controller2.example.com:9093,3@controller3.example.com:9093</code></pre>
- <p>Every broker and controller must set the <code>controller.quorum.voters</code> property. The node ID supplied in the <code>controller.quorum.voters</code> property must match the corresponding id on the controller servers. For example, on controller1, node.id must be set to 1, and so forth. Each node ID must be unique across all the servers in a particular cluster. No two servers can have the same node ID regardless of their <code>process.roles<code> values.
+ <p>Every broker and controller must set the <code>controller.quorum.voters</code> property. The node ID supplied in the <code>controller.quorum.voters</code> property must match the corresponding id on the controller servers. For example, on controller1, node.id must be set to 1, and so forth. Each node ID must be unique across all the servers in a particular cluster. No two servers can have the same node ID regardless of their <code>process.roles</code> values.
<h4 class="anchor-heading"><a id="kraft_storage" class="anchor-link"></a><a href="#kraft_storage">Storage Tool</a></h4>
<p></p>
@@ -3474,7 +3474,7 @@ CurrentObservers: [0,1,2]</code></pre>
<h5 class="anchor-heading"><a id="kraft_shell_tool" class="anchor-link"></a><a href="#kraft_shell_tool">Metadata Shell</a></h5>
- <p>The <code>kafka-metadata-shell<code> tool can be used to interactively inspect the state of the cluster metadata partition:</p>
+ <p>The <code>kafka-metadata-shell</code> tool can be used to interactively inspect the state of the cluster metadata partition:</p>
<pre class="line-numbers"><code class="language-bash">
> bin/kafka-metadata-shell.sh --snapshot metadata_log_dir/__cluster_metadata-0/00000000000000000000.log