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 1e465576 [auto] Generated docs from Apache Ozone master
182bd53bef9c3233330c792feffc796277b14c43
1e465576 is described below
commit 1e4655767c91d54b2eb47fdfb2458663d362652a
Author: Github Actions <[email protected]>
AuthorDate: Wed Feb 5 12:45:54 2025 +0000
[auto] Generated docs from Apache Ozone master
182bd53bef9c3233330c792feffc796277b14c43
---
docs/edge/en/sitemap.xml | 6 +++---
docs/edge/feature/erasurecoding.html | 8 ++++----
docs/edge/feature/om-ha.html | 4 ++--
docs/edge/feature/snapshot.html | 6 +++---
docs/edge/interface/ofs.html | 2 +-
docs/edge/sitemap.xml | 2 +-
docs/edge/zh/interface/ofs.html | 2 +-
7 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/docs/edge/en/sitemap.xml b/docs/edge/en/sitemap.xml
index 2b219ba7..7c1cbed0 100644
--- a/docs/edge/en/sitemap.xml
+++ b/docs/edge/en/sitemap.xml
@@ -81,7 +81,7 @@
/>
</url><url>
<loc>/feature/om-ha.html</loc>
- <lastmod>2025-01-06T08:40:12+01:00</lastmod>
+ <lastmod>2025-02-05T15:47:32+05:30</lastmod>
<xhtml:link
rel="alternate"
hreflang="zh"
@@ -94,7 +94,7 @@
/>
</url><url>
<loc>/feature/erasurecoding.html</loc>
- <lastmod>2024-03-24T23:03:07+08:00</lastmod>
+ <lastmod>2025-02-05T15:47:32+05:30</lastmod>
<xhtml:link
rel="alternate"
hreflang="zh"
@@ -107,7 +107,7 @@
/>
</url><url>
<loc>/feature/snapshot.html</loc>
- <lastmod>2024-04-01T12:52:48+05:30</lastmod>
+ <lastmod>2025-02-05T15:47:32+05:30</lastmod>
</url><url>
<loc>/feature/scm-ha.html</loc>
<lastmod>2025-01-21T00:21:41-08:00</lastmod>
diff --git a/docs/edge/feature/erasurecoding.html
b/docs/edge/feature/erasurecoding.html
index 7f27373e..4792def0 100644
--- a/docs/edge/feature/erasurecoding.html
+++ b/docs/edge/feature/erasurecoding.html
@@ -515,7 +515,7 @@ approach which is expensive. The Apache Ozone supports
<code>RATIS/THREE</code>
The Ozone default replication scheme <code>RATIS/THREE</code> has 200%
overhead in storage
space and other resources (e.g., network bandwidth).
However, for warm and cold datasets with relatively low I/O activities,
additional
-block replicas rarely accessed during normal operations, but still consume the
same
+block replicas are rarely accessed during normal operations, but still consume
the same
amount of resources as the first replica.</p>
<p>Therefore, a natural improvement is to use Erasure Coding (EC) in place of
replication,
which provides the same level of fault-tolerance with much less storage space.
@@ -639,7 +639,7 @@ any replication config or bucket does not have any default
values.</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 sh bucket create <bucket path> --type
EC --replication rs-6-3-1024k
</span></span></code></pre></div><p>We can also reset the EC Replication
Config with the following command.</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 sh bucket set-replication-config <bucket
path> --type EC --replication rs-3-2-1024k
-</span></span></code></pre></div><p>Once we reset, only newly created keys
take effect of this new setting. Prior created keys in the bucket stay with
same older setting.</p>
+</span></span></code></pre></div><p>Once we reset, only newly created keys
will take effect of this new setting. Prior created keys in the bucket stay
with same older setting.</p>
<h4 id="setting-ec-replication-config-while-creating-keysfiles">Setting EC
Replication Config While Creating Keys/Files</h4>
<p>We can pass the EC Replication Config while creating the keys irrespective
of bucket Replication Config.</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 sh key put <Ozone Key Object Path>
<Local File> --type EC --replication rs-6-3-1024k
@@ -659,7 +659,7 @@ storage applications. Enabling ISA-L allows significantly
improve EC performance
<h4 id="prerequisites">Prerequisites</h4>
<p>To enable ISA-L you will also require Hadoop native libraries
(libhadoop.so).</p>
<h4 id="installation">Installation</h4>
-<p>Both libraries should be placed to the directory specified by the
java.library.path property or set by <code>LD_LIBRARY_PATH</code> environment
variable.
+<p>Both libraries should be placed in the directory specified by the
java.library.path property or set by <code>LD_LIBRARY_PATH</code> environment
variable.
The default value of java.library.path depends on the OS and Java version. For
example, on Linux with OpenJDK 8 it is
<code>/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib</code>.</p>
<h4 id="verification">Verification</h4>
<p>You can check if ISA-L is accessible to Ozone by running the following
command:</p>
@@ -683,7 +683,7 @@ The default value of java.library.path depends on the OS
and Java version. For e
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.0.0-SNAPSHOT, Last Modified: March 24, 2024 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/b267a578313da15cb0b5e40fddc4d003c8c222d4";>b267a57831</a>
+ Version: 2.0.0-SNAPSHOT, Last Modified: February 5, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/1a9cf6cfe0f288da76d5adbe7066998bae39ba33";>1a9cf6cfe0</a>
</span>
</div>
</footer>
diff --git a/docs/edge/feature/om-ha.html b/docs/edge/feature/om-ha.html
index 73a899bd..bc99a3a7 100644
--- a/docs/edge/feature/om-ha.html
+++ b/docs/edge/feature/om-ha.html
@@ -558,7 +558,7 @@ s=d.getElementsByTagName('script')[0];
<h2 id="om-bootstrap">OM Bootstrap</h2>
<p>To convert a non-HA OM to be HA or to add new OM nodes to existing HA OM
ring, new OM node(s) need to be bootstrapped.</p>
<p>Before bootstrapping a new OM node, all the existing OM’s on-disk
configuration file (ozone-site.xml) must be updated with the configuration
details
-of the new OM such as nodeId, address, port etc. Note that the existing
OM’s need not be restarted. They will reload the configuration from disk
when
+of the new OM such as nodeId, address, port etc. Note that the existing OMs
need not be restarted. They will reload the configuration from disk when
they receive a bootstrap request from the bootstrapping node.</p>
<p>To bootstrap an OM, the following command needs to be run:</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 om <span style="color:#f92672">[</span>global
options <span style="color:#f92672">(</span>optional<span
style="color:#f92672">)]</span> --bootstrap
@@ -590,7 +590,7 @@ using the <em>force</em> option. The <em>force</em> option
allows to continue wi
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.0.0-SNAPSHOT, Last Modified: January 6, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/8f2689dfe5f9b79e64f7d78acbaaf300c1ccbd1c";>8f2689dfe5</a>
+ Version: 2.0.0-SNAPSHOT, Last Modified: February 5, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/1a9cf6cfe0f288da76d5adbe7066998bae39ba33";>1a9cf6cfe0</a>
</span>
</div>
</footer>
diff --git a/docs/edge/feature/snapshot.html b/docs/edge/feature/snapshot.html
index 562cb912..ba8280d5 100644
--- a/docs/edge/feature/snapshot.html
+++ b/docs/edge/feature/snapshot.html
@@ -514,7 +514,7 @@ s=d.getElementsByTagName('script')[0];
<h2 id="snapshot-apis">Snapshot APIs</h2>
<p>Snapshot feature is available through ‘ozone fs’ and
‘ozone sh’ CLI. This feature can also be programmatically accessed
from Ozone <code>ObjectStore</code> Java client. The feature provides following
functionalities:</p>
<ul>
-<li>Create Snapshot: Create an instantenous snapshot for a given bucket</li>
+<li>Create Snapshot: Create an instantaneous snapshot for a given bucket</li>
</ul>
<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 sh snapshot create <span
style="color:#f92672">[</span>-hV<span style="color:#f92672">]</span>
<bucket> <span style="color:#f92672">[</span><snapshotName><span
style="color:#f92672">]</span>
</span></span></code></pre></div><ul>
@@ -544,7 +544,7 @@ Ozone also provides SnapshotDiff API. Whenever a user
issues a SnapshotDiff betw
<h2 id="deployment">Deployment</h2>
<hr>
<h3 id="cluster-and-hardware-configuration">Cluster and Hardware
Configuration</h3>
-<p>Snapshot feature places additional demands on the cluster in terms of CPU,
memory and storage. Cluster nodes running Ozone Managers and Ozone Datanodes
should be configured with extra storage capacity depending on the number of
active snapshots that the user wants to keep. Ozone Snapshots consume
incremental amount of space per snapshot. e.g. if the active object store has
100 GB data (before replication) and a snapshot is taken, then the 100 GB of
space will be locked in that snapsho [...]
+<p>Snapshot feature places additional demands on the cluster in terms of CPU,
memory and storage. Cluster nodes running Ozone Managers and Ozone Datanodes
should be configured with extra storage capacity depending on the number of
active snapshots that the user wants to keep. Ozone Snapshots consume an
incremental amount of space per snapshot. e.g. if the active object store has
100 GB data (before replication) and a snapshot is taken, then the 100 GB of
space will be locked in that snap [...]
<p>Similarly, nodes running Ozone Manager should be configured with extra
memory depending on how many snapshots are concurrently read from. This also
depends on how many concurrent SnapshotDiff jobs are expected in the cluster.
By default, an Ozone Manager allows 10 concurrent SnapshotDiff jobs at a time,
which can be increased in config.</p>
@@ -565,7 +565,7 @@ Ozone also provides SnapshotDiff API. Whenever a user
issues a SnapshotDiff betw
<footer class="footer">
<div class="container">
<span class="small text-muted">
- Version: 2.0.0-SNAPSHOT, Last Modified: April 1, 2024 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/83d75861b0266160b219acde72d769eb0f9d5ac4";>83d75861b0</a>
+ Version: 2.0.0-SNAPSHOT, Last Modified: February 5, 2025 <a
class="hide-child link primary-color"
href="https://github.com/apache/ozone/commit/1a9cf6cfe0f288da76d5adbe7066998bae39ba33";>1a9cf6cfe0</a>
</span>
</div>
</footer>
diff --git a/docs/edge/interface/ofs.html b/docs/edge/interface/ofs.html
index 611c0ccb..cd053731 100644
--- a/docs/edge/interface/ofs.html
+++ b/docs/edge/interface/ofs.html
@@ -556,7 +556,7 @@ For example:</p>
<p>Or use the put command to write a file to the bucket.</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-bash" data-lang="bash"><span style="display:flex;"><span>hdfs
dfs -put /etc/hosts /volume1/bucket1/test</span></span></code></pre></div>
<p>For more usage, see: <a
href="https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf";>https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf</a></p>
-<h2 id="differences-from-o3fshahahugoshortcode95s5hbhb">Differences from <a
href="../interface/o3fs.html">o3fs</a></h2>
+<h2 id="differences-from-o3fshahahugoshortcode96s5hbhb">Differences from <a
href="../interface/o3fs.html">o3fs</a></h2>
<h3 id="creating-files">Creating files</h3>
<p>OFS doesn’t allow creating keys(files) directly under root or volumes.
Users will receive an error message when they try to do that:</p>
diff --git a/docs/edge/sitemap.xml b/docs/edge/sitemap.xml
index 9cd75675..03e32260 100644
--- a/docs/edge/sitemap.xml
+++ b/docs/edge/sitemap.xml
@@ -4,7 +4,7 @@
<sitemap>
<loc>/en/sitemap.xml</loc>
- <lastmod>2025-01-21T00:21:41-08:00</lastmod>
+ <lastmod>2025-02-05T15:47:32+05:30</lastmod>
</sitemap>
diff --git a/docs/edge/zh/interface/ofs.html b/docs/edge/zh/interface/ofs.html
index 90c059e7..801ed68e 100644
--- a/docs/edge/zh/interface/ofs.html
+++ b/docs/edge/zh/interface/ofs.html
@@ -478,7 +478,7 @@ ofs://omservice/tmp/key1
<p>或者使用 put 命令向桶中写入一个文件</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-bash" data-lang="bash"><span style="display:flex;"><span>hdfs
dfs -put /etc/hosts /volume1/bucket1/test</span></span></code></pre></div>
<p>有关更多用法，请参见： <a
href="https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf";>https://issues.apache.org/jira/secure/attachment/12987636/Design%20ofs%20v1.pdf</a></p>
-<h2 id="与-o3fshahahugoshortcode96s5hbhb-的区别">与 <a
href="../../zh/interface/o3fs.html">o3fs</a> 的区别</h2>
+<h2 id="与-o3fshahahugoshortcode95s5hbhb-的区别">与 <a
href="../../zh/interface/o3fs.html">o3fs</a> 的区别</h2>
<h3 id="创建文件">创建文件</h3>
<p>OFS 不允许直接在根目录或卷下创建键（文件）。
当用户尝试这样做时，他们将收到一个错误消息：</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
