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 cdb9d0cc [auto] Generated docs from Apache Ozone master
275b95c1220723f464376abe1b81cc989aabd4b9
cdb9d0cc is described below
commit cdb9d0ccb361b91de6ec8fbd125bafec06f68691
Author: Github Actions <[email protected]>
AuthorDate: Tue Sep 23 12:46:36 2025 +0000
[auto] Generated docs from Apache Ozone master
275b95c1220723f464376abe1b81cc989aabd4b9
---
docs/edge/design.html | 10 ++++
docs/edge/design/index.xml | 9 ++-
.../om-bootstrapping-with-snapshots.html | 65 +++++++--------------
docs/edge/en/sitemap.xml | 10 ++--
docs/edge/feature.html | 41 ++++---------
docs/edge/feature/decommission.html | 68 +++++++++++++++++++++-
docs/edge/feature/index.xml | 7 ---
docs/edge/feature/observability.html | 17 +++---
.../feature/s3-multi-tenancy-access-control.html | 2 +-
docs/edge/index.xml | 4 +-
docs/edge/sitemap.xml | 4 +-
docs/edge/zh/feature/observability.html | 16 ++---
docs/edge/zh/sitemap.xml | 2 +-
13 files changed, 142 insertions(+), 113 deletions(-)
diff --git a/docs/edge/design.html b/docs/edge/design.html
index acaa32d0..3d719f63 100644
--- a/docs/edge/design.html
+++ b/docs/edge/design.html
@@ -587,6 +587,16 @@ s=d.getElementsByTagName('script')[0];
<td>implementing</td>
</tr>
+ <tr>
+ <td>2025-08-05</td>
+ <td>
+ <a
href="https://issues.apache.org/jira/browse/HDDS-12090";>HDDS-12090</a>
+ </td>
+ <td><a
href="./design/om-bootstrapping-with-snapshots.html">OM Bootstrapping with
Snapshots</a></td>
+ <td>Design for the OM bootstrapping process that
is snapshot aware</td>
+ <td>implemented</td>
+ </tr>
+
<tr>
<td>2025-05-12</td>
<td>
diff --git a/docs/edge/design/index.xml b/docs/edge/design/index.xml
index 2a7c9cc5..ba28b6de 100644
--- a/docs/edge/design/index.xml
+++ b/docs/edge/design/index.xml
@@ -6,7 +6,7 @@
<description>Recent content in Designs on Ozone</description>
<generator>Hugo</generator>
<language>en</language>
- <lastBuildDate>Wed, 03 Sep 2025 11:34:46 -0700</lastBuildDate>
+ <lastBuildDate>Mon, 22 Sep 2025 10:13:03 -0700</lastBuildDate>
<atom:link href="/design/index.xml" rel="self" type="application/rss+xml"
/>
<item>
<title>Listener Ozone Manager</title>
@@ -15,6 +15,13 @@
<guid>/design/listener-om.html</guid>
<description>Read-only Ozone Manager to scale out read
performance.</description>
</item>
+ <item>
+ <title>OM Bootstrapping with Snapshots</title>
+ <link>/design/om-bootstrapping-with-snapshots.html</link>
+ <pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate>
+ <guid>/design/om-bootstrapping-with-snapshots.html</guid>
+ <description>Design for the OM bootstrapping process that is snapshot
aware</description>
+ </item>
<item>
<title>Full Volume Handling</title>
<link>/design/full-volume-handling.html</link>
diff --git a/docs/edge/feature/om-bootstrapping-with-snapshots.html
b/docs/edge/design/om-bootstrapping-with-snapshots.html
similarity index 96%
rename from docs/edge/feature/om-bootstrapping-with-snapshots.html
rename to docs/edge/design/om-bootstrapping-with-snapshots.html
index ca503c64..267e592a 100644
--- a/docs/edge/feature/om-bootstrapping-with-snapshots.html
+++ b/docs/edge/design/om-bootstrapping-with-snapshots.html
@@ -46,9 +46,8 @@ s=d.getElementsByTagName('script')[0];
</head>
-<body>
+ <body>
-
<nav class="navbar navbar-inverse navbar-fixed-top">
<div class="container-fluid">
<div class="navbar-header">
@@ -76,11 +75,9 @@ s=d.getElementsByTagName('script')[0];
</div>
</nav>
-
- <div class="wrapper">
- <div class="container-fluid">
- <div class="row">
-
+ <div class="container-fluid">
+ <div class="row">
+
<div class="col-sm-2 col-md-2 sidebar" id="sidebar">
<ul class="nav nav-sidebar">
@@ -560,32 +557,20 @@ s=d.getElementsByTagName('script')[0];
</div>
- <div class="col-sm-10 col-sm-offset-2 col-md-10 col-md-offset-2
main-content">
-
+ <div class="col-sm-9 col-sm-offset-3 col-md-10 col-md-offset-2
main-content">
+ <div class="col-md-9">
+ <h1><a
href="https://issues.apache.org/jira/browse/HDDS-12090";>[HDDS-12090]</a> OM
Bootstrapping with Snapshots (implemented) </h1>
+ <div><i>Authors: Swaminathan Balachandran</i><div
class="pull-right">2025-08-05</div></div>
+ <p> </p>
+ <div class="panel panel-success">
+ <div class="panel-heading">Summary</div>
+ <div class="panel-body">
+ Design for the OM bootstrapping process that is
snapshot aware
+ </div>
+ </div>
- <div class="col-md-9">
- <nav aria-label="breadcrumb">
- <ol class="breadcrumb">
- <li class="breadcrumb-item"><a
href="../index.html">Home</a></li>
- <li class="breadcrumb-item" aria-current="page"><a
href="../feature.html">Features</a></li>
- <li class="breadcrumb-item active" aria-current="page">OM
Bootstrapping with Snapshots</li>
- </ol>
- </nav>
-
-
-
-<div class="pull-right">
-
-
-
-</div>
-
-
- <div class="col-md-9">
- <h1>OM Bootstrapping with Snapshots</h1>
-
- <!--
+ <!--
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
@@ -724,25 +709,18 @@ Following is the flow for creating the tarball:</p>
<p>Approach 1 is the most optimized solution as it balances the amount of time
under the lock by minimising the amount of IO ops inside the lock by
introducing another threshold config to track this. Moreover taking this
approach will also need the most minimal amount of code change as it doesn’t
differ from the current approach by much. While approach 2 might look simpler
but this would imply revamping the entire bootstrap logic currently in place
and moreover this approach might increa [...]
<p>Final approach implemented is the Approach 1.1</p>
-
-
- <a class="btn btn-success btn-lg"
href="../feature/faircallqueue.html">Next >></a>
-
- </div>
+ </div>
</div>
</div>
</div>
- </div>
- <div class="push"></div>
- </div>
-
+
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.1.0-SNAPSHOT, Last Modified: August 9, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/31cab30b6e49045872999fe24c4cdad9c6de9af5";>31cab30b6e</a>
+ Version: 2.1.0-SNAPSHOT, Last Modified: September 22, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/3ddcd48228bb4c6f75b3effbf8959c75fe616bc0";>3ddcd48228</a>
</span>
</div>
</footer>
@@ -754,6 +732,5 @@ Following is the flow for creating the tarball:</p>
<script src="../js/bootstrap.min.js"></script>
-</body>
-
-</html>
\ No newline at end of file
+ </body>
+</html>
diff --git a/docs/edge/en/sitemap.xml b/docs/edge/en/sitemap.xml
index 8ab69a34..1d1c0d82 100644
--- a/docs/edge/en/sitemap.xml
+++ b/docs/edge/en/sitemap.xml
@@ -68,7 +68,7 @@
/>
</url><url>
<loc>/feature/decommission.html</loc>
- <lastmod>2025-02-05T18:57:09+05:30</lastmod>
+ <lastmod>2025-09-22T10:13:03-07:00</lastmod>
<xhtml:link
rel="alternate"
hreflang="zh"
@@ -552,7 +552,7 @@
/>
</url><url>
<loc>/feature/observability.html</loc>
- <lastmod>2025-06-05T21:06:30-04:00</lastmod>
+ <lastmod>2025-09-22T21:20:12+05:30</lastmod>
<xhtml:link
rel="alternate"
hreflang="zh"
@@ -708,13 +708,13 @@
/>
</url><url>
<loc>/design.html</loc>
- <lastmod>2025-09-03T11:34:46-07:00</lastmod>
+ <lastmod>2025-09-22T10:13:03-07:00</lastmod>
</url><url>
<loc>/design/listener-om.html</loc>
<lastmod>2025-09-03T11:34:46-07:00</lastmod>
</url><url>
- <loc>/feature/om-bootstrapping-with-snapshots.html</loc>
- <lastmod>2025-08-09T02:25:09+05:30</lastmod>
+ <loc>/design/om-bootstrapping-with-snapshots.html</loc>
+ <lastmod>2025-09-22T10:13:03-07:00</lastmod>
</url><url>
<loc>/tools/debug.html</loc>
<lastmod>2025-09-04T19:14:00+05:30</lastmod>
diff --git a/docs/edge/feature.html b/docs/edge/feature.html
index a8713f78..3d9a44ab 100644
--- a/docs/edge/feature.html
+++ b/docs/edge/feature.html
@@ -934,29 +934,6 @@ s=d.getElementsByTagName('script')[0];
- <div class="col-sm-6">
- <div class="card">
- <div class="card-body">
- <h2 class="card-title">
-
- OM Bootstrapping with Snapshots
- </h2>
- <p class="card-text">Design for the OM
bootstrapping process that is snapshot aware</p>
- <a
href="./feature/om-bootstrapping-with-snapshots.html"
- class=" btn btn-primary btn-lg">OM
Bootstrapping with Snapshots</a>
- </div>
- </div>
- </div>
-
-
- </div>
-
-
-
-
-
- <div class="row">
-
<div class="col-sm-6">
<div class="card">
<div class="card-body">
@@ -992,10 +969,14 @@ There is no implementation for gRPC yet.</p></p>
</div>
+ </div>
+
+ <div class="row">
+
<div class="col-sm-6">
<div class="card">
<div class="card-body">
@@ -1011,14 +992,10 @@ There is no implementation for gRPC yet.</p></p>
</div>
- </div>
-
- <div class="row">
-
<div class="col-sm-6">
<div class="card">
<div class="card-body">
@@ -1034,10 +1011,14 @@ There is no implementation for gRPC yet.</p></p>
</div>
+ </div>
+
+ <div class="row">
+
<div class="col-sm-6">
<div class="card">
<div class="card-body">
@@ -1053,14 +1034,10 @@ There is no implementation for gRPC yet.</p></p>
</div>
- </div>
-
- <div class="row">
-
<div class="col-sm-6">
<div class="card">
<div class="card-body">
@@ -1076,6 +1053,8 @@ There is no implementation for gRPC yet.</p></p>
</div>
+ </div>
+
</div>
diff --git a/docs/edge/feature/decommission.html
b/docs/edge/feature/decommission.html
index aac0d731..cafa4d6b 100644
--- a/docs/edge/feature/decommission.html
+++ b/docs/edge/feature/decommission.html
@@ -635,7 +635,71 @@ s=d.getElementsByTagName('script')[0];
<p><strong>Note:</strong> To recommission a datanode you may execute the below
command in cli,</p>
<div class="highlight"><pre tabindex="0"
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-shell" data-lang="shell"><span
style="display:flex;"><span>ozone admin datanode recommission <span
style="color:#f92672">[</span>-hV<span style="color:#f92672">]</span> <span
style="color:#f92672">[</span>-id<span
style="color:#f92672">=</span><scmServiceId><span
style="color:#f92672">]</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">[</span>--scm<span
style="color:#f92672">=</span><scm><span style="color:#f92672">]</span>
<span style="color:#f92672">[</span><hosts>...<span
style="color:#f92672">]</span>
-</span></span></code></pre></div><h1 id="om-decommission">OM Decommission</h1>
+</span></span></code></pre></div><h3
id="tuning-and-monitoring-decommissioning">Tuning and Monitoring
Decommissioning</h3>
+<p>The process of decommissioning a DataNode involves replicating all its
containers to other DataNodes in the cluster. The speed of this process can be
tuned, and its progress can be monitored using several configuration properties
and metrics.</p>
+<h4 id="configuration-properties">Configuration Properties</h4>
+<p>Administrators can adjust the following properties in
<code>ozone-site.xml</code> to control the container replication speed during
decommissioning. They are grouped by the component where they are primarily
configured.</p>
+<h5 id="scm-side-properties">SCM-Side Properties</h5>
+<ul>
+<li><strong><code>hdds.scm.replication.datanode.replication.limit</code></strong>
+<ul>
+<li><strong>Purpose</strong>: Defines the base limit for concurrent
replication commands that the SCM will <em>send</em> to a single DataNode.</li>
+<li><strong>Default</strong>: <code>20</code>.</li>
+<li><strong>Details</strong>: The effective limit for a decommissioning
DataNode is this value multiplied by
<code>hdds.datanode.replication.outofservice.limit.factor</code>.</li>
+</ul>
+</li>
+</ul>
+<h5 id="datanode-side-properties">DataNode-Side Properties</h5>
+<ul>
+<li>
+<p><strong><code>hdds.datanode.replication.outofservice.limit.factor</code></strong></p>
+<ul>
+<li><strong>Purpose</strong>: A multiplier to increase replication capacity
for <code>DECOMMISSIONING</code> or <code>MAINTENANCE</code> nodes. This is a
key property for tuning decommission speed.</li>
+<li><strong>Default</strong>: <code>2.0</code>.</li>
+<li><strong>Details</strong>: Although this is a DataNode property, it must
also be set in the SCM’s configuration. The SCM uses it to send more
replication commands, and the DataNode uses it to increase its internal
resources (threads and queues) to handle the increased load.</li>
+</ul>
+</li>
+<li>
+<p><strong><code>hdds.datanode.replication.queue.limit</code></strong></p>
+<ul>
+<li><strong>Purpose</strong>: Sets the base size of the queue for incoming
replication requests on a DataNode.</li>
+<li><strong>Default</strong>: <code>4096</code>.</li>
+<li><strong>Details</strong>: For decommissioning nodes, this limit is scaled
by <code>hdds.datanode.replication.outofservice.limit.factor</code>.</li>
+</ul>
+</li>
+<li>
+<p><strong><code>hdds.datanode.replication.streams.limit</code></strong></p>
+<ul>
+<li><strong>Purpose</strong>: Sets the base number of threads for the
replication thread pool on a DataNode.</li>
+<li><strong>Default</strong>: <code>10</code>.</li>
+<li><strong>Details</strong>: For decommissioning nodes, this limit is also
scaled by <code>hdds.datanode.replication.outofservice.limit.factor</code>.</li>
+</ul>
+</li>
+</ul>
+<p>By tuning these properties, administrators can balance the decommissioning
speed against the impact on the cluster’s performance.</p>
+<h4 id="metrics">Metrics</h4>
+<p>The following metrics can be used to monitor the progress of DataNode
decommissioning. The names in parentheses are the corresponding Prometheus
metric names, which may vary slightly depending on the metrics sink
configuration.</p>
+<h5 id="scm-side-metrics-replicationmanagermetrics">SCM-side Metrics
(<code>ReplicationManagerMetrics</code>)</h5>
+<p>These metrics are available on the SCM and provide a cluster-wide view of
the replication process. During decommissioning, you should see an increase in
these metrics. The name in parentheses is the corresponding Prometheus metric
name.</p>
+<ul>
+<li><code>InflightReplication</code>
(<code>replication_manager_metrics_inflight_replication</code>): The number of
container replication requests currently in progress.</li>
+<li><code>replicationCmdsSentTotal</code>
(<code>replication_manager_metrics_replication_cmds_sent_total</code>): The
total number of replication commands sent to datanodes.</li>
+<li><code>replicasCreatedTotal</code>
(<code>replication_manager_metrics_replicas_created_total</code>): The total
number of container replicas successfully created.</li>
+<li><code>replicateContainerCmdsDeferredTotal</code>
(<code>replication_manager_metrics_replicate_container_cmds_deferred_total</code>):
The number of replication commands deferred because source datanodes were
overloaded. If this value is high, it might indicate that the source datanodes
(including the decommissioning one) are too busy.</li>
+</ul>
+<h5 id="datanode-side-metrics-measuredreplicator-metrics">Datanode-side
Metrics (<code>MeasuredReplicator</code> metrics)</h5>
+<p>These metrics are available on each DataNode. For a decommissioning node,
they show its activity as a source of replicas. For other nodes, they show
their activity as targets. The name in parentheses is the corresponding
Prometheus metric name.</p>
+<ul>
+<li><code>success</code> (<code>measured_replicator_success</code>): The
number of successful replication tasks.</li>
+<li><code>successTime</code> (<code>measured_replicator_success_time</code>):
The total time spent on successful replication tasks.</li>
+<li><code>transferredBytes</code>
(<code>measured_replicator_transferred_bytes</code>): The total bytes
transferred for successful replications.</li>
+<li><code>failure</code> (<code>measured_replicator_failure</code>): The
number of failed replication tasks.</li>
+<li><code>failureTime</code> (<code>measured_replicator_failure_time</code>):
The total time spent on failed replication tasks.</li>
+<li><code>failureBytes</code>
(<code>measured_replicator_failure_bytes</code>): The total bytes that failed
to be transferred.</li>
+<li><code>queueTime</code> (<code>measured_replicator_queue_time</code>): The
total time tasks spend in the replication queue. A high value might indicate
the datanode is overloaded.</li>
+</ul>
+<p>By monitoring these metrics, administrators can get a clear picture of the
decommissioning progress and identify potential bottlenecks.</p>
+<h1 id="om-decommission">OM Decommission</h1>
<p>Ozone Manager (OM) decommissioning is the process in which you gracefully
remove one of the OM from the OM HA Ring.</p>
<p>To decommission an OM and remove the node from the OM HA ring, the
following steps need to be executed.</p>
<ol>
@@ -680,7 +744,7 @@ other OMs.</li>
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.1.0-SNAPSHOT, Last Modified: February 5, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/d8c94fb9a90eba68cc655f9690461b5f42d209c4";>d8c94fb9a9</a>
+ Version: 2.1.0-SNAPSHOT, Last Modified: September 22, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/3ddcd48228bb4c6f75b3effbf8959c75fe616bc0";>3ddcd48228</a>
</span>
</div>
</footer>
diff --git a/docs/edge/feature/index.xml b/docs/edge/feature/index.xml
index 2a8910d1..6e194a74 100644
--- a/docs/edge/feature/index.xml
+++ b/docs/edge/feature/index.xml
@@ -133,13 +133,6 @@
<guid>/feature/s3-multi-tenancy-access-control.html</guid>
<description>Access Control with Ranger in Ozone
Multi-Tenancy</description>
</item>
- <item>
- <title>OM Bootstrapping with Snapshots</title>
- <link>/feature/om-bootstrapping-with-snapshots.html</link>
- <pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate>
- <guid>/feature/om-bootstrapping-with-snapshots.html</guid>
- <description>Design for the OM bootstrapping process that is snapshot
aware</description>
- </item>
<item>
<title></title>
<link>/feature/faircallqueue.html</link>
diff --git a/docs/edge/feature/observability.html
b/docs/edge/feature/observability.html
index 5b6144c8..41b98151 100644
--- a/docs/edge/feature/observability.html
+++ b/docs/edge/feature/observability.html
@@ -650,19 +650,18 @@ s=d.getElementsByTagName('script')[0];
<img src="GrafanaOzoneRPCMetrics.png" alt='RPC dashboard'
class="img-responsive" /></p>
<h2 id="distributed-tracing">Distributed tracing</h2>
-<p>Distributed tracing can help to understand performance bottleneck with
visualizing end-to-end performance.</p>
-<p>Ozone uses <a href="https://jaegertracing.io";>jaeger</a> tracing library to
collect traces which can send tracing data to any compatible backend (Zipkin,
…).</p>
+<p>Distributed tracing can help to understand performance bottleneck with
visualizing end-to-end performance.
+Ozone makes use of <a href="https://opentelemetry.io/";>OpenTelemetry</a> API
for tracing and uses otlp with Grpc format for sending traces.
+<a href="https://jaegertracing.io";>jaeger</a> tracing library as collector can
collect traces from Ozone over default port 4317 (as default).</p>
<p>Tracing is turned off by default, but can be turned on with
<code>hdds.tracing.enabled</code> from <code>ozone-site.xml</code></p>
<div class="highlight"><pre tabindex="0"
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="display:flex;"><span><span
style="color:#f92672"><property></span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672"><name></span>hdds.tracing.enabled<span
style="color:#f92672"></name></span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672"><value></span>true<span
style="color:#f92672"></value></span>
</span></span><span style="display:flex;"><span><span
style="color:#f92672"></property></span>
-</span></span></code></pre></div><p>Jaeger client can be configured with
environment variables as documented <a
href="https://github.com/jaegertracing/jaeger-client-java/blob/master/jaeger-core/README.md";>here</a>:</p>
-<p>For example:</p>
-<div class="highlight"><pre tabindex="0"
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-shell" data-lang="shell"><span
style="display:flex;"><span>JAEGER_SAMPLER_PARAM<span
style="color:#f92672">=</span>0.01
-</span></span><span style="display:flex;"><span>JAEGER_SAMPLER_TYPE<span
style="color:#f92672">=</span>probabilistic
-</span></span><span style="display:flex;"><span>JAEGER_AGENT_HOST<span
style="color:#f92672">=</span>jaeger
-</span></span></code></pre></div><p>This configuration will record 1% of the
requests to limit the performance overhead. For more information about jaeger
sampling <a
href="https://www.jaegertracing.io/docs/1.18/sampling/#client-sampling-configuration";>check
the documentation</a></p>
+</span></span></code></pre></div><p>Below are the configuration steps for
setting the collector endpoint and sampling strategy. Set these environment
variables to be set for each Ozone component (OM, SCM, datanode) and for the
Ozone client to enable tracing.</p>
+<pre tabindex="0"><code>OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
+OTEL_TRACES_SAMPLER_ARG=0.01
+</code></pre><p>This configuration will record 1% of the requests to limit the
performance overhead.</p>
<h2 id="ozone-insight">ozone insight</h2>
<p>Ozone insight is a swiss-army-knife tool to for checking the current state
of Ozone cluster. It can show logging, metrics and configuration for a
particular component.</p>
<p>To check the available components use <code>ozone insight list</code>:</p>
@@ -794,7 +793,7 @@ s=d.getElementsByTagName('script')[0];
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.1.0-SNAPSHOT, Last Modified: June 5, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/c13a3fed9ecf8e0b457009ad8d56e60e3a983ced";>c13a3fed9e</a>
+ Version: 2.1.0-SNAPSHOT, Last Modified: September 22, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/8887a14030fcd0ad0e285b42f6b9fab5956200ea";>8887a14030</a>
</span>
</div>
</footer>
diff --git a/docs/edge/feature/s3-multi-tenancy-access-control.html
b/docs/edge/feature/s3-multi-tenancy-access-control.html
index 1aef4d05..c2db3531 100644
--- a/docs/edge/feature/s3-multi-tenancy-access-control.html
+++ b/docs/edge/feature/s3-multi-tenancy-access-control.html
@@ -684,7 +684,7 @@ they could edit the bucket policies on their own, for
example, to share the buck
- <a class="btn btn-success btn-lg"
href="../feature/om-bootstrapping-with-snapshots.html">Next >></a>
+ <a class="btn btn-success btn-lg"
href="../feature/faircallqueue.html">Next >></a>
</div>
diff --git a/docs/edge/index.xml b/docs/edge/index.xml
index f6117978..1a82ddc0 100644
--- a/docs/edge/index.xml
+++ b/docs/edge/index.xml
@@ -492,9 +492,9 @@
</item>
<item>
<title>OM Bootstrapping with Snapshots</title>
- <link>/feature/om-bootstrapping-with-snapshots.html</link>
+ <link>/design/om-bootstrapping-with-snapshots.html</link>
<pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate>
- <guid>/feature/om-bootstrapping-with-snapshots.html</guid>
+ <guid>/design/om-bootstrapping-with-snapshots.html</guid>
<description>Design for the OM bootstrapping process that is snapshot
aware</description>
</item>
<item>
diff --git a/docs/edge/sitemap.xml b/docs/edge/sitemap.xml
index adc4f9ed..ab158906 100644
--- a/docs/edge/sitemap.xml
+++ b/docs/edge/sitemap.xml
@@ -4,14 +4,14 @@
<sitemap>
<loc>/en/sitemap.xml</loc>
- <lastmod>2025-09-19T13:18:09-07:00</lastmod>
+ <lastmod>2025-09-22T10:13:03-07:00</lastmod>
</sitemap>
<sitemap>
<loc>/zh/sitemap.xml</loc>
- <lastmod>2025-08-12T20:20:41+05:30</lastmod>
+ <lastmod>2025-09-22T21:20:12+05:30</lastmod>
</sitemap>
diff --git a/docs/edge/zh/feature/observability.html
b/docs/edge/zh/feature/observability.html
index 2f1ecd25..27498ca8 100644
--- a/docs/edge/zh/feature/observability.html
+++ b/docs/edge/zh/feature/observability.html
@@ -462,18 +462,17 @@ s=d.getElementsByTagName('script')[0];
</span></span><span style="display:flex;"><span> - <span
style="color:#e6db74">"127.0.0.1:9876"</span>
</span></span></code></pre></div><h2 id="分布式跟踪">分布式跟踪</h2>
<p>分布式跟踪可以通过可视化端到端的性能来帮助了解性能瓶颈。</p>
-<p>Ozone 使用 <a href="https://jaegertracing.io";>jaeger</a>
跟踪库收集跟踪，可以将跟踪数据发送到任何兼容的后端(Zipkin，…)。</p>
+<p>Ozone 使用 <a href="https://opentelemetry.io/";>OpenTelemetry</a> API 进行跟踪，并使用
Grpc 格式的 otlp 发送跟踪信息。
+jaeger 跟踪库作为收集器可以通过默认端口 4317（默认）从 Ozone 收集跟踪信息。</p>
<p>默认情况下，跟踪功能是关闭的，可以通过 <code>ozon-site.xml</code> 的
<code>hdds.tracing.enabled</code> 配置变量打开。</p>
<div class="highlight"><pre tabindex="0"
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="display:flex;"><span><span
style="color:#f92672"><property></span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672"><name></span>hdds.tracing.enabled<span
style="color:#f92672"></name></span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672"><value></span>true<span
style="color:#f92672"></value></span>
</span></span><span style="display:flex;"><span><span
style="color:#f92672"></property></span>
-</span></span></code></pre></div><p>Jaeger 客户端可以用环境变量进行配置，如<a
href="https://github.com/jaegertracing/jaeger-client-java/blob/master/jaeger-core/README.md";>这份</a>文档所述。</p>
-<p>例如：</p>
-<div class="highlight"><pre tabindex="0"
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-shell" data-lang="shell"><span
style="display:flex;"><span>JAEGER_SAMPLER_PARAM<span
style="color:#f92672">=</span>0.01
-</span></span><span style="display:flex;"><span>JAEGER_SAMPLER_TYPE<span
style="color:#f92672">=</span>probabilistic
-</span></span><span style="display:flex;"><span>JAEGER_AGENT_HOST<span
style="color:#f92672">=</span>jaeger
-</span></span></code></pre></div><p>此配置将记录1%的请求，以限制性能开销。有关 Jaeger
抽样的更多信息，请查看<a
href="https://www.jaegertracing.io/docs/1.18/sampling/#client-sampling-configuration";>文档</a>。</p>
+</span></span></code></pre></div><p>以下是提供收集器端点和采样策略所需的配置。这些是需要为每个 Ozone
组件（OM、SCM、DataNode）和 Ozone 客户端设置的环境变量，以启用 Shell 等跟踪功能。</p>
+<pre tabindex="0"><code>OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317
+OTEL_TRACES_SAMPLER_ARG=0.01
+</code></pre><p>此配置将记录1%的请求，以限制性能开销。</p>
<h2 id="ozone-insight">Ozone Insight</h2>
<p>Ozone Insight 是一个用于检查 Ozone 集群当前状态的工具，它可以显示特定组件的日志记录、指标和配置。</p>
<p>请使用<code>ozone insight list</code>命令检查可用的组件：</p>
@@ -587,6 +586,7 @@ s=d.getElementsByTagName('script')[0];
<p>实际上 <code>ozone insight</code> 是通过 HTTP
端点来检索所需的信息（<code>/conf</code>、<code>/prom</code>和<code>/logLevel</code>端点），它在安全环境中还不被支持。</p>
</div>
+
</div>
@@ -602,7 +602,7 @@ s=d.getElementsByTagName('script')[0];
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.1.0-SNAPSHOT, Last Modified: April 11, 2022 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/2522127b1c0bc12038265faeb667c9c0592e53bc";>2522127b1c</a>
+ Version: 2.1.0-SNAPSHOT, Last Modified: September 22, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/8887a14030fcd0ad0e285b42f6b9fab5956200ea";>8887a14030</a>
</span>
</div>
</footer>
diff --git a/docs/edge/zh/sitemap.xml b/docs/edge/zh/sitemap.xml
index be9de021..63c78f14 100644
--- a/docs/edge/zh/sitemap.xml
+++ b/docs/edge/zh/sitemap.xml
@@ -484,7 +484,7 @@
/>
</url><url>
<loc>/zh/feature/observability.html</loc>
- <lastmod>2022-04-11T19:12:00+02:00</lastmod>
+ <lastmod>2025-09-22T21:20:12+05:30</lastmod>
<xhtml:link
rel="alternate"
hreflang="en"
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
