This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 95e6597e [auto] Generated docs from Apache Ozone master
fefaf9beeaa2354e7f4baf9f4fed535df849d45f
95e6597e is described below
commit 95e6597ef450f32baaa096b0f5049b357d72a36a
Author: Github Actions <[email protected]>
AuthorDate: Tue Jan 21 12:45:31 2025 +0000
[auto] Generated docs from Apache Ozone master
fefaf9beeaa2354e7f4baf9f4fed535df849d45f
---
docs/edge/en/sitemap.xml | 2 +-
docs/edge/feature/scm-ha.html | 27 ++++++++++-----------------
docs/edge/sitemap.xml | 4 ++--
docs/edge/zh/feature/scm-ha.html | 28 ++++++++--------------------
docs/edge/zh/sitemap.xml | 2 +-
5 files changed, 22 insertions(+), 41 deletions(-)
diff --git a/docs/edge/en/sitemap.xml b/docs/edge/en/sitemap.xml
index c89893e4..2b219ba7 100644
--- a/docs/edge/en/sitemap.xml
+++ b/docs/edge/en/sitemap.xml
@@ -110,7 +110,7 @@
<lastmod>2024-04-01T12:52:48+05:30</lastmod>
</url><url>
<loc>/feature/scm-ha.html</loc>
- <lastmod>2024-11-06T18:31:29+08:00</lastmod>
+ <lastmod>2025-01-21T00:21:41-08:00</lastmod>
<xhtml:link
rel="alternate"
hreflang="zh"
diff --git a/docs/edge/feature/scm-ha.html b/docs/edge/feature/scm-ha.html
index 2ffcbc5e..d26d149a 100644
--- a/docs/edge/feature/scm-ha.html
+++ b/docs/edge/feature/scm-ha.html
@@ -513,12 +513,7 @@ s=d.getElementsByTagName('script')[0];
<p>Both Ozone Manager and Storage Container Manager supports HA. In this mode
the internal state is replicated via RAFT (with Apache Ratis)</p>
<p>This document explains the HA setup of Storage Container Manager (SCM),
please check <a href="../feature/om-ha.html">this page</a> for HA setup of
Ozone Manager (OM). While they can be setup for HA independently, a reliable,
full HA setup requires enabling HA for both services.</p>
<h2 id="configuration">Configuration</h2>
-<p>HA mode of Storage Container Manager can be enabled with the following
settings in <code>ozone-site.xml</code>:</p>
-<div class="highlight"><pre
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code
class="language-XML" data-lang="XML"><span
style="color:#f92672"><property></span>
- <span style="color:#f92672"><name></span>ozone.scm.ratis.enable<span
style="color:#f92672"></name></span>
- <span style="color:#f92672"><value></span>true<span
style="color:#f92672"></value></span>
-<span style="color:#f92672"></property></span>
-</code></pre></div><p>One Ozone configuration (<code>ozone-site.xml</code>)
can support multiple SCM HA node set, multiple Ozone clusters. To select
between the available SCM nodes a logical name is required for each of the
clusters which can be resolved to the IP addresses (and domain names) of the
Storage Container Managers.</p>
+<p>One Ozone configuration (<code>ozone-site.xml</code>) can support multiple
SCM HA node set, multiple Ozone clusters. To select between the available SCM
nodes a logical name is required for each of the clusters which can be resolved
to the IP addresses (and domain names) of the Storage Container Managers.</p>
<p>This logical name is called <code>serviceId</code> and can be configured in
the <code>ozone-site.xml</code></p>
<p>Most of the time you need to set only the values of your current
cluster:</p>
<div class="highlight"><pre
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code
class="language-XML" data-lang="XML"><span
style="color:#f92672"><property></span>
@@ -604,15 +599,13 @@ signed certificate for sub-CA from root CA.</p>
<p><strong>Note</strong>: Make sure to run <strong>–init</strong> only
on one of the SCM host if
primordial SCM is not defined. Bring up other SCM’s using
<strong>–bootstrap</strong>.</p>
<h3 id="current-scm-ha-security-limitation">Current SCM HA Security
limitation:</h3>
-<ol>
-<li>When primordial SCM is down, new SCM’s cannot be bootstrapped and join the
-quorum.</li>
-<li>Secure cluster upgrade to ratis-enable secure cluster is not
supported.</li>
-</ol>
+<ul>
+<li>Unsecure HA cluster upgrade to secure HA cluster is not supported.</li>
+</ul>
<h2 id="implementation-details">Implementation details</h2>
<p>SCM HA uses Apache Ratis to replicate state between the members of the SCM
HA quorum. Each node maintains the block management metadata in local
RocksDB.</p>
<p>This replication process is a simpler version of OM HA replication process
as it doesn’t use any double buffer (as the overall db thourghput of SCM
requests are lower)</p>
-<p>Datanodes are sending all the reports (Container reports, Pipeline
reports…) to <em>all</em> the Datanodes parallel. Only the leader node
can assign/create new containers, and only the leader node sends command back
to the Datanodes.</p>
+<p>Datanodes are sending all the reports (Container reports, Pipeline
reports…) to <em>all</em> SCM nodes in parallel. Only the leader node
can assign/create new containers, and only the leader node sends commands back
to the Datanodes.</p>
<h2 id="verify-scm-ha-setup">Verify SCM HA setup</h2>
<p>After starting an SCM-HA it can be validated if the SCM nodes are forming
one single quorum instead of 3 individual SCM nodes.</p>
<p>First, check if all the SCM nodes store the same ClusterId metadata:</p>
@@ -633,10 +626,10 @@ bin/ozone debug ldb --db<span
style="color:#f92672">=</span>/tmp/metadata/scm.db
bin/ozone debug ldb --db<span
style="color:#f92672">=</span>/tmp/metadata/scm.db scan --column-family<span
style="color:#f92672">=</span>containers
-</code></pre></div><h2 id="migrating-from-existing-scm">Migrating from
existing SCM</h2>
-<p>SCM HA can be turned on on any Ozone cluster. First enable Ratis
(<code>ozone.scm.ratis.enable</code>) and configure only one node for the Ratis
ring (<code>ozone.scm.nodes.serviceId</code> should have one element).</p>
-<p>Start the cluster and test if it works well.</p>
-<p>If everything is fine, you can extend the cluster configuration with
multiple nodes, restart SCM node, and initialize the additional nodes with
<code>scm --bootstrap</code> command.</p>
+</code></pre></div><h2 id="migrating-from-non-ha-to-ha-scm">Migrating from
Non-HA to HA SCM</h2>
+<p>Add additional SCM nodes and extend the cluster configuration to reflect
the newly added nodes.
+Bootstrap the newly added SCM nodes with <code>scm --bootstrap</code> command
and start the SCM service.
+Note: Make sure that the <code>ozone.scm.primordial.node.id</code> property is
pointed to the existing SCM before you run the <code>bootstrap</code> command
on the newly added SCM nodes.</p>
@@ -656,7 +649,7 @@ bin/ozone debug ldb --db<span
style="color:#f92672">=</span>/tmp/metadata/scm.db
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.0.0-SNAPSHOT, Last Modified: November 6, 2024 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/2547ac0438ec0374f75227f60a35b11ad9a986a4";>2547ac0438</a>
+ Version: 2.0.0-SNAPSHOT, Last Modified: January 21, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/7b4df04beb59373f0dda509adeb59a33feb488fd";>7b4df04beb</a>
</span>
</div>
</footer>
diff --git a/docs/edge/sitemap.xml b/docs/edge/sitemap.xml
index 799e25db..e5ce50a9 100644
--- a/docs/edge/sitemap.xml
+++ b/docs/edge/sitemap.xml
@@ -4,14 +4,14 @@
<sitemap>
<loc>en/sitemap.xml</loc>
- <lastmod>2025-01-19T01:04:54-08:00</lastmod>
+ <lastmod>2025-01-21T00:21:41-08:00</lastmod>
</sitemap>
<sitemap>
<loc>zh/sitemap.xml</loc>
- <lastmod>2025-01-06T08:40:12+01:00</lastmod>
+ <lastmod>2025-01-21T00:21:41-08:00</lastmod>
</sitemap>
diff --git a/docs/edge/zh/feature/scm-ha.html b/docs/edge/zh/feature/scm-ha.html
index 38255726..b9a0491c 100644
--- a/docs/edge/zh/feature/scm-ha.html
+++ b/docs/edge/zh/feature/scm-ha.html
@@ -441,18 +441,7 @@ s=d.getElementsByTagName('script')[0];
<p>Ozone Manager 和 Storage Container Manager 都支持 HA。在这种模式下，内部状态通过 RAFT (使用
Apache Ratis )复制。</p>
<p>本文档解释了 Storage Container Manager (SCM)的 HA 设置，请在<a
href="../../zh/feature/om-ha.html">本页</a>中查看 Ozone Manager (OM)的 HA
设置。虽然它们可以独立地为 HA 进行设置，但可靠的、完全的 HA 设置需要为两个服务启用 HA。</p>
<h2 id="配置">配置</h2>
-<blockquote>
-<p>⚠️ <strong>注意</strong> ⚠️</p>
-<p>SCM HA 目前仅支持新初始化的集群。
-SCM HA 必须在 Ozone 服务首次启动前开启。
-当某个 SCM 以非 HA 的模式启动后，不支持将其改为 HA 模式。</p>
-</blockquote>
-<p>Storage Container Manager 的 HA 模式可以在 <code>ozone-site.xml</code>
中进行以下设置：</p>
-<div class="highlight"><pre
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code
class="language-XML" data-lang="XML"><span
style="color:#f92672"><property></span>
- <span style="color:#f92672"><name></span>ozone.scm.ratis.enable<span
style="color:#f92672"></name></span>
- <span style="color:#f92672"><value></span>true<span
style="color:#f92672"></value></span>
-<span style="color:#f92672"></property></span>
-</code></pre></div><p>一个 Ozone 配置(<code>ozone-site.xml</code>)可以支持多个SCM
HA节点集，多个 Ozone 集群。要在可用的 SCM 节点之间进行选择，每个集群都需要一个逻辑名称，可以将其解析为 Storage Container
Manage 的 IP 地址(和域名)。</p>
+<p>一个 Ozone 配置(<code>ozone-site.xml</code>)可以支持多个SCM HA节点集，多个 Ozone 集群。要在可用的
SCM 节点之间进行选择，每个集群都需要一个逻辑名称，可以将其解析为 Storage Container Manage 的 IP 地址(和域名)。</p>
<p>这个逻辑名称称为 <code>serviceId</code>，可以在 <code>ozone-site.xml</code> 中配置。</p>
<p>大多数情况下，你只需要设置当前集群的值：</p>
<div class="highlight"><pre
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code
class="language-XML" data-lang="XML"><span
style="color:#f92672"><property></span>
@@ -527,10 +516,9 @@ SCM 使用子 CA 证书来签署 OM/Datanodes 的证书。</p>
<p><strong>注意</strong>: 当原始 SCM 未定义时，请确保仅在一个 SCM 上运行
<strong>–init</strong>，
在其他 SCM 节点上需使用 <strong>–bootstrap</strong> 进行引导。</p>
<h3 id="目前-scm-ha-安全的限制">目前 SCM HA 安全的限制</h3>
-<ol>
-<li>当原始 SCM 失效时, 新的 SCM 不能被引导并添加到 HA 节点中。</li>
+<ul>
<li>尚未支持从非 HA 安全集群升级到 HA 安全集群。</li>
-</ol>
+</ul>
<h2 id="实现细节">实现细节</h2>
<p>SCM HA 使用 Apache Ratis 在 SCM HA 仲裁的成员之间复制状态。每个节点在本地 RocksDB 中维护块管理元数据。</p>
<p>这个复制过程是 OM HA 复制过程的一个简单版本，因为它不使用任何双缓冲区(SCM 请求的总体 db 吞吐量更低)。</p>
@@ -555,10 +543,10 @@ bin/ozone debug ldb --db<span
style="color:#f92672">=</span>/tmp/metadata/scm.db
bin/ozone debug ldb --db<span
style="color:#f92672">=</span>/tmp/metadata/scm.db scan --column-family<span
style="color:#f92672">=</span>containers
-</code></pre></div><h2 id="从现有的scm迁移">从现有的SCM迁移</h2>
-<p>可以在任何 Ozone 集群上打开 SCM HA。 首先启用 Ratis（<code>ozone.scm.ratis.enable</code>）并为
Ratis ring 配置一个节点（<code>ozone.scm.nodes.serviceId</code> 应该有一个元素）。</p>
-<p>启动集群并测试它是否正常工作。</p>
-<p>如果一切正常，您可以用多个节点扩展集群配置，重新启动 SCM 节点，并使用 <code>scm --bootstrap</code>
命令初始化其他节点。</p>
+</code></pre></div><h2 id="从非ha-scm迁移到scm-ha">从非HA SCM迁移到SCM HA</h2>
+<p>添加额外的 SCM 节点，并扩展集群配置以包含新添加的节点。
+使用 <code>scm --bootstrap</code> 命令为新添加的 SCM 节点引导启动，然后启动 SCM 服务。
+注意：在新添加的 SCM 节点上运行 bootstrap 命令之前，请确保
<code>ozone.scm.primordial.node.id</code> 属性指向现有的 SCM。</p>
@@ -578,7 +566,7 @@ bin/ozone debug ldb --db<span
style="color:#f92672">=</span>/tmp/metadata/scm.db
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.0.0-SNAPSHOT, Last Modified: March 25, 2023 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/7357f752e481037e7d4eb2a05b61f9cb15323f1e";>7357f752e4</a>
+ Version: 2.0.0-SNAPSHOT, Last Modified: January 21, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/7b4df04beb59373f0dda509adeb59a33feb488fd";>7b4df04beb</a>
</span>
</div>
</footer>
diff --git a/docs/edge/zh/sitemap.xml b/docs/edge/zh/sitemap.xml
index 8e8f2fea..ad54d6d0 100644
--- a/docs/edge/zh/sitemap.xml
+++ b/docs/edge/zh/sitemap.xml
@@ -120,7 +120,7 @@
/>
</url><url>
<loc>/zh/feature/scm-ha.html</loc>
- <lastmod>2023-03-25T14:10:09-07:00</lastmod>
+ <lastmod>2025-01-21T00:21:41-08:00</lastmod>
<xhtml:link
rel="alternate"
hreflang="en"
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
