This is an automated email from the ASF dual-hosted git repository.
Russole pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/master by this push:
new 449d6523da HDDS-14733. Standardize the usage of the term IO in the
documentation (#486)
449d6523da is described below
commit 449d6523da666ecf74b06666589af5b3edd84b22
Author: Chia-Yi Chiu <[email protected]>
AuthorDate: Tue Jul 7 01:30:42 2026 +0900
HDDS-14733. Standardize the usage of the term IO in the documentation (#486)
---
docs/03-core-concepts/06-comparison.md | 2 +-
docs/04-user-guide/02-integrations/08-hadoop-distcp.md | 2 +-
docs/05-administrator-guide/02-configuration/99-appendix.md | 12 ++++++------
.../03-operations/04-disk-replacement/03-datanodes.md | 4 ++--
.../version-2.1.0/03-core-concepts/06-comparison.md | 2 +-
.../04-user-guide/03-integrations/08-hadoop-distcp.md | 2 +-
.../03-operations/04-disk-replacement/03-datanodes.md | 4 ++--
.../version-2.1.1/03-core-concepts/06-comparison.md | 2 +-
.../04-user-guide/03-integrations/08-hadoop-distcp.md | 2 +-
.../03-operations/04-disk-replacement/03-datanodes.md | 4 ++--
10 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/docs/03-core-concepts/06-comparison.md
b/docs/03-core-concepts/06-comparison.md
index 050b47e996..9714c66e09 100644
--- a/docs/03-core-concepts/06-comparison.md
+++ b/docs/03-core-concepts/06-comparison.md
@@ -26,7 +26,7 @@ Ozone shines when users are in need of an Apache licensed,
strongly consistent s
| Tech | Type | Consistency | Scale | Big Data Integration | Performance Focus
| Notes |
| ---- | ---- | ----------- | ----- | -------------------- | -----------------
| ----- |
-| **Isilon (Dell PowerScale)** | File (Scale-Out NAS) | Strong | PBs, billions
of files | Indirect | High throughput, good mixed IO | Enterprise NAS, POSIX
compliant, good for mixed workloads, backup, analytics |
+| **Isilon (Dell PowerScale)** | File (Scale-Out NAS) | Strong | PBs, billions
of files | Indirect | High throughput, good mixed I/O | Enterprise NAS, POSIX
compliant, good for mixed workloads, backup, analytics |
| **VAST** | File / Object | Strong | PBs | Yes, AI workloads | Ultra-low
latency, all-flash NVMe | All-flash, NFS/S3, great for AI/ML and large
unstructured datasets |
| **WEKA** | Parallel File | Strong | PBs | HPC, AI | Ultra-low latency, high
IOPS | High-performance file, GPU clusters, NFS/SMB/S3 |
| **Spectrum Scale (GPFS)** | File (POSIX) | Strong | PBs | HPC, AI | High
throughput, scale-out metadata | IBM, used in HPC/AI, policy tiering, good
POSIX compliance |
diff --git a/docs/04-user-guide/02-integrations/08-hadoop-distcp.md
b/docs/04-user-guide/02-integrations/08-hadoop-distcp.md
index 23c2c80a97..09442b5369 100644
--- a/docs/04-user-guide/02-integrations/08-hadoop-distcp.md
+++ b/docs/04-user-guide/02-integrations/08-hadoop-distcp.md
@@ -101,7 +101,7 @@ This helps the client correctly engage in secure
communication protocols with Oz
When issuing DistCp commands (or other HDFS-compatible commands like `hdfs dfs
-ls`) against an Ozone cluster in a different Kerberos realm than the client or
source/destination cluster, Ozone 1.x versions may produce an error similar to:
```text
-24/02/07 18:47:36 INFO retry.RetryInvocationHandler:
com.google.protobuf.ServiceException: java.io.IOException: DestHost:destPort
host1.dst.example.com:9862, LocalHost:localPort
host1.src.example.com/10.140.99.144:0. Failed on local exception:
java.io.IOException: Couldn't set up IO streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
om/[email protected], expecting: OM/host1.dst.example.com@REALM,
while invoking $Proxy10.submitRequest over no [...]
+24/02/07 18:47:36 INFO retry.RetryInvocationHandler:
com.google.protobuf.ServiceException: java.io.IOException: DestHost:destPort
host1.dst.example.com:9862, LocalHost:localPort
host1.src.example.com/10.140.99.144:0. Failed on local exception:
java.io.IOException: Couldn't set up I/O streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
om/[email protected], expecting: OM/host1.dst.example.com@REALM,
while invoking $Proxy10.submitRequest over n [...]
```
**Cause:**
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index 7452d57c17..a4c8ff999b 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -125,17 +125,17 @@ This page provides a comprehensive overview of the
configuration keys available
| `hdds.datanode.disk.balancer.should.run.default` | false | `DATANODE`,
`DISKBALANCER` | If DiskBalancer fails to get information from
diskbalancer.info, it will choose this value to decide if this service should
be running. |
| `hdds.datanode.disk.balancer.stop.after.disk.even` | true | `DISKBALANCER` |
If true, the DiskBalancer will automatically stop once disks are balanced. |
| `hdds.datanode.disk.balancer.volume.density.threshold.percent` | 10 |
`DISKBALANCER` | Threshold is a percentage in the range of 0 to 100. A datanode
is considered balanced if for each volume, the utilization of the volume(used
space to capacity ratio) differs from the utilization of the datanode(used
space to capacity ratio of the entire datanode) no more than the threshold. |
-| `hdds.datanode.disk.check.io.failures.tolerated` | 1 | `DATANODE` | The
number of IO tests out of the last `hdds.datanode.disk.check.io.test.count`
test run that are allowed to fail before the volume is marked as failed. |
+| `hdds.datanode.disk.check.io.failures.tolerated` | 1 | `DATANODE` | The
number of I/O tests out of the last `hdds.datanode.disk.check.io.test.count`
test run that are allowed to fail before the volume is marked as failed. |
| `hdds.datanode.disk.check.io.file.size` | 100B | `DATANODE` | The size of
the temporary file that will be synced to the disk and read back to assess its
health. The contents of the file will be stored in memory during the duration
of the check. |
-| `hdds.datanode.disk.check.io.test.count` | 3 | `DATANODE` | The number of IO
tests required to determine if a disk has failed. Each disk check does one IO
test. The volume will be failed if more than
`hdds.datanode.disk.check.io.failures.tolerated` out of the last
`hdds.datanode.disk.check.io.test.count` runs failed. Set to 0 to disable disk
IO checks. |
-| `hdds.datanode.disk.check.io.test.enabled` | true | `DATANODE` | The
configuration to enable or disable disk IO checks. |
+| `hdds.datanode.disk.check.io.test.count` | 3 | `DATANODE` | The number of
I/O tests required to determine if a disk has failed. Each disk check does one
I/O test. The volume will be failed if more than
`hdds.datanode.disk.check.io.failures.tolerated` out of the last
`hdds.datanode.disk.check.io.test.count` runs failed. Set to 0 to disable disk
I/O checks. |
+| `hdds.datanode.disk.check.io.test.enabled` | true | `DATANODE` | The
configuration to enable or disable disk I/O checks. |
| `hdds.datanode.disk.check.min.gap` | 10m | `DATANODE` | The minimum gap
between two successive checks of the same Datanode volume. Unit could be
defined with postfix (ns,ms,s,m,h,d). |
-| `hdds.datanode.disk.check.rocksdb.check.io.test.enabled` | true | `DATANODE`
| The configuration to enable or disable RocksDb disk IO checks. |
+| `hdds.datanode.disk.check.rocksdb.check.io.test.enabled` | true | `DATANODE`
| The configuration to enable or disable RocksDb disk I/O checks. |
| `hdds.datanode.disk.check.sliding.window.timeout` | 70m | `DATANODE` | Time
interval after which a disk check failure result stored in the sliding window
will expire. Do not set the window timeout period to less than or equal to the
disk check interval period or failures can be missed across sparse checks e.g.,
every 120m interval with a 60m window rarely accumulates enough failed events
Unit could be defined with postfix (ns,ms,s,m,h,d). |
| `hdds.datanode.disk.check.timeout` | 10m | `DATANODE` | Maximum allowed time
for a disk check to complete. If the check does not complete within this time
interval then the disk is declared as failed. Unit could be defined with
postfix (ns,ms,s,m,h,d). |
| `hdds.datanode.disk.check.timeout.failures.tolerated` | 1 | `DATANODE` | The
number of volume check timeouts allowed within the timeout sliding window
before the volume is marked as failed. |
| `hdds.datanode.disk.check.timeout.sliding.window.timeout` | 90m | `DATANODE`
| Time interval after which a timed out volume check event stored in the
timeout sliding window will expire. Do not set this below the periodic disk
check interval or timeout events may not accumulate across sparse checks. Unit
could be defined with postfix (ns,ms,s,m,h,d). |
-| `hdds.datanode.disk.check.timeout.test.enabled` | true | `DATANODE` | Enable
or disable timeout-based volume failure tracking independently of the disk IO
health checks. |
+| `hdds.datanode.disk.check.timeout.test.enabled` | true | `DATANODE` | Enable
or disable timeout-based volume failure tracking independently of the disk I/O
health checks. |
| `hdds.datanode.dns.interface` | default | `OZONE`, `DATANODE` | The name of
the Network Interface from which a Datanode should report its IP address. e.g.
eth2. This setting may be required for some multi-homed nodes where the
Datanodes are assigned multiple hostnames and it is desirable for the Datanodes
to use a non-default hostname. |
| `hdds.datanode.dns.nameserver` | default | `OZONE`, `DATANODE` | The host
name or IP address of the name server (DNS) which a Datanode should use to
determine its own host name. |
| `hdds.datanode.du.factory.classname` | | `DATANODE` | The fully qualified
name of the factory class that creates objects for providing disk space usage
information. It should implement the SpaceUsageCheckFactory interface. |
@@ -568,7 +568,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `ozone.om.snapshot.rename.allowed` | false | `OZONE`, `OM` | Allows the
Ozone snapshot rename operation if set to true on the OM side. Blocks it
otherwise. |
| `ozone.om.snapshot.rocksdb.metrics.enabled` | false | `OZONE`, `OM` | Skip
collecting RocksDBStore metrics for Snapshotted DB. |
| `ozone.om.transport.class` |
org.apache.hadoop.ozone.om.protocolPB.Hadoop3OmTransportFactory | `OM`,
`MANAGEMENT` | Property to determine the transport protocol for the client to
Ozone Manager channel. |
-| `ozone.om.unflushed.transaction.max.count` | 10000 | `OZONE`, `OM` | the
unflushed transactions here are those requests that have been applied to OM
state machine but not been flushed to OM rocksdb. when OM meets high
concurrency-pressure and flushing is not fast enough, too many pending requests
will be hold in memory and will lead to long GC of OM, which will slow down
flushing further. there are some cases that flushing is slow, for example, 1
rocksdb is on a HDD, which has poor IO [...]
+| `ozone.om.unflushed.transaction.max.count` | 10000 | `OZONE`, `OM` | the
unflushed transactions here are those requests that have been applied to OM
state machine but not been flushed to OM rocksdb. when OM meets high
concurrency-pressure and flushing is not fast enough, too many pending requests
will be hold in memory and will lead to long GC of OM, which will slow down
flushing further. there are some cases that flushing is slow, for example, 1
rocksdb is on a HDD, which has poor I/O [...]
| `ozone.om.upgrade.finalization.ratis.based.timeout` | 30s | `OM`, `UPGRADE`
| Maximum time to wait for a slow follower to be finalized through a Ratis
snapshot. This is an advanced config, and needs to be changed only under a
special circumstance when the leader OM has purged the finalize request from
its logs, and a follower OM was down during upgrade finalization. Default is
30s. |
| `ozone.om.upgrade.quota.recalculate.enabled` | true | `OZONE`, `OM` | quota
recalculation trigger when upgrade to the layout version QUOTA. while upgrade,
re-calculation of quota used will block write operation to existing buckets
till this operation is completed. |
| `ozone.om.user.max.volume` | 1024 | `OM`, `MANAGEMENT` | The maximum number
of volumes a user can have on a cluster.Increasing or decreasing this number
has no real impact on ozone cluster. This is defined only for operational
purposes. Only an administrator can create a volume, once a volume is created
there are no restrictions on the number of buckets or keys inside each bucket a
user can create. |
diff --git
a/docs/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
b/docs/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
index 528600c6df..6de09c29b5 100644
---
a/docs/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
+++
b/docs/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
@@ -130,8 +130,8 @@ Additional properties control disk health check behavior:
| Property | Default | Description |
|----------|---------|-------------|
-| `hdds.datanode.disk.check.io.test.count` | `3` | Number of IO tests required
to determine failure. Set to `0` to disable IO checks. |
-| `hdds.datanode.disk.check.io.failures.tolerated` | `1` | IO test failures
allowed before marking volume as failed |
+| `hdds.datanode.disk.check.io.test.count` | `3` | Number of I/O tests
required to determine failure. Set to `0` to disable I/O checks. |
+| `hdds.datanode.disk.check.io.failures.tolerated` | `1` | I/O test failures
allowed before marking volume as failed |
| `hdds.datanode.disk.check.io.file.size` | `100B` | Size of temporary file
used for I/O health checks |
| `hdds.datanode.disk.check.min.gap` | `10m` | Minimum time gap between
successive checks of the same volume |
| `hdds.datanode.disk.check.timeout` | `10m` | Maximum time allowed for a disk
check to complete |
diff --git a/versioned_docs/version-2.1.0/03-core-concepts/06-comparison.md
b/versioned_docs/version-2.1.0/03-core-concepts/06-comparison.md
index 6e2e53393f..aab93354b5 100644
--- a/versioned_docs/version-2.1.0/03-core-concepts/06-comparison.md
+++ b/versioned_docs/version-2.1.0/03-core-concepts/06-comparison.md
@@ -26,7 +26,7 @@ Ozone shines when users are in need of an Apache licensed,
strongly consistent s
| Tech | Type | Consistency | Scale | Big Data Integration | Performance Focus
| Notes |
| ---- | ---- | ----------- | ----- | -------------------- | -----------------
| ----- |
-| **Isilon (Dell PowerScale)** | File (Scale-Out NAS) | Strong | PBs, billions
of files | Indirect | High throughput, good mixed IO | Enterprise NAS, POSIX
compliant, good for mixed workloads, backup, analytics |
+| **Isilon (Dell PowerScale)** | File (Scale-Out NAS) | Strong | PBs, billions
of files | Indirect | High throughput, good mixed I/O | Enterprise NAS, POSIX
compliant, good for mixed workloads, backup, analytics |
| **VAST** | File / Object | Strong | PBs | Yes, AI workloads | Ultra-low
latency, all-flash NVMe | All-flash, NFS/S3, great for AI/ML and large
unstructured datasets |
| **WEKA** | Parallel File | Strong | PBs | HPC, AI | Ultra-low latency, high
IOPS | High-performance file, GPU clusters, NFS/SMB/S3 |
| **Spectrum Scale (GPFS)** | File (POSIX) | Strong | PBs | HPC, AI | High
throughput, scale-out metadata | IBM, used in HPC/AI, policy tiering, good
POSIX compliance |
diff --git
a/versioned_docs/version-2.1.0/04-user-guide/03-integrations/08-hadoop-distcp.md
b/versioned_docs/version-2.1.0/04-user-guide/03-integrations/08-hadoop-distcp.md
index 23c2c80a97..09442b5369 100644
---
a/versioned_docs/version-2.1.0/04-user-guide/03-integrations/08-hadoop-distcp.md
+++
b/versioned_docs/version-2.1.0/04-user-guide/03-integrations/08-hadoop-distcp.md
@@ -101,7 +101,7 @@ This helps the client correctly engage in secure
communication protocols with Oz
When issuing DistCp commands (or other HDFS-compatible commands like `hdfs dfs
-ls`) against an Ozone cluster in a different Kerberos realm than the client or
source/destination cluster, Ozone 1.x versions may produce an error similar to:
```text
-24/02/07 18:47:36 INFO retry.RetryInvocationHandler:
com.google.protobuf.ServiceException: java.io.IOException: DestHost:destPort
host1.dst.example.com:9862, LocalHost:localPort
host1.src.example.com/10.140.99.144:0. Failed on local exception:
java.io.IOException: Couldn't set up IO streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
om/[email protected], expecting: OM/host1.dst.example.com@REALM,
while invoking $Proxy10.submitRequest over no [...]
+24/02/07 18:47:36 INFO retry.RetryInvocationHandler:
com.google.protobuf.ServiceException: java.io.IOException: DestHost:destPort
host1.dst.example.com:9862, LocalHost:localPort
host1.src.example.com/10.140.99.144:0. Failed on local exception:
java.io.IOException: Couldn't set up I/O streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
om/[email protected], expecting: OM/host1.dst.example.com@REALM,
while invoking $Proxy10.submitRequest over n [...]
```
**Cause:**
diff --git
a/versioned_docs/version-2.1.0/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
b/versioned_docs/version-2.1.0/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
index 528600c6df..6de09c29b5 100644
---
a/versioned_docs/version-2.1.0/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
+++
b/versioned_docs/version-2.1.0/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
@@ -130,8 +130,8 @@ Additional properties control disk health check behavior:
| Property | Default | Description |
|----------|---------|-------------|
-| `hdds.datanode.disk.check.io.test.count` | `3` | Number of IO tests required
to determine failure. Set to `0` to disable IO checks. |
-| `hdds.datanode.disk.check.io.failures.tolerated` | `1` | IO test failures
allowed before marking volume as failed |
+| `hdds.datanode.disk.check.io.test.count` | `3` | Number of I/O tests
required to determine failure. Set to `0` to disable I/O checks. |
+| `hdds.datanode.disk.check.io.failures.tolerated` | `1` | I/O test failures
allowed before marking volume as failed |
| `hdds.datanode.disk.check.io.file.size` | `100B` | Size of temporary file
used for I/O health checks |
| `hdds.datanode.disk.check.min.gap` | `10m` | Minimum time gap between
successive checks of the same volume |
| `hdds.datanode.disk.check.timeout` | `10m` | Maximum time allowed for a disk
check to complete |
diff --git a/versioned_docs/version-2.1.1/03-core-concepts/06-comparison.md
b/versioned_docs/version-2.1.1/03-core-concepts/06-comparison.md
index 6e2e53393f..aab93354b5 100644
--- a/versioned_docs/version-2.1.1/03-core-concepts/06-comparison.md
+++ b/versioned_docs/version-2.1.1/03-core-concepts/06-comparison.md
@@ -26,7 +26,7 @@ Ozone shines when users are in need of an Apache licensed,
strongly consistent s
| Tech | Type | Consistency | Scale | Big Data Integration | Performance Focus
| Notes |
| ---- | ---- | ----------- | ----- | -------------------- | -----------------
| ----- |
-| **Isilon (Dell PowerScale)** | File (Scale-Out NAS) | Strong | PBs, billions
of files | Indirect | High throughput, good mixed IO | Enterprise NAS, POSIX
compliant, good for mixed workloads, backup, analytics |
+| **Isilon (Dell PowerScale)** | File (Scale-Out NAS) | Strong | PBs, billions
of files | Indirect | High throughput, good mixed I/O | Enterprise NAS, POSIX
compliant, good for mixed workloads, backup, analytics |
| **VAST** | File / Object | Strong | PBs | Yes, AI workloads | Ultra-low
latency, all-flash NVMe | All-flash, NFS/S3, great for AI/ML and large
unstructured datasets |
| **WEKA** | Parallel File | Strong | PBs | HPC, AI | Ultra-low latency, high
IOPS | High-performance file, GPU clusters, NFS/SMB/S3 |
| **Spectrum Scale (GPFS)** | File (POSIX) | Strong | PBs | HPC, AI | High
throughput, scale-out metadata | IBM, used in HPC/AI, policy tiering, good
POSIX compliance |
diff --git
a/versioned_docs/version-2.1.1/04-user-guide/03-integrations/08-hadoop-distcp.md
b/versioned_docs/version-2.1.1/04-user-guide/03-integrations/08-hadoop-distcp.md
index 23c2c80a97..09442b5369 100644
---
a/versioned_docs/version-2.1.1/04-user-guide/03-integrations/08-hadoop-distcp.md
+++
b/versioned_docs/version-2.1.1/04-user-guide/03-integrations/08-hadoop-distcp.md
@@ -101,7 +101,7 @@ This helps the client correctly engage in secure
communication protocols with Oz
When issuing DistCp commands (or other HDFS-compatible commands like `hdfs dfs
-ls`) against an Ozone cluster in a different Kerberos realm than the client or
source/destination cluster, Ozone 1.x versions may produce an error similar to:
```text
-24/02/07 18:47:36 INFO retry.RetryInvocationHandler:
com.google.protobuf.ServiceException: java.io.IOException: DestHost:destPort
host1.dst.example.com:9862, LocalHost:localPort
host1.src.example.com/10.140.99.144:0. Failed on local exception:
java.io.IOException: Couldn't set up IO streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
om/[email protected], expecting: OM/host1.dst.example.com@REALM,
while invoking $Proxy10.submitRequest over no [...]
+24/02/07 18:47:36 INFO retry.RetryInvocationHandler:
com.google.protobuf.ServiceException: java.io.IOException: DestHost:destPort
host1.dst.example.com:9862, LocalHost:localPort
host1.src.example.com/10.140.99.144:0. Failed on local exception:
java.io.IOException: Couldn't set up I/O streams:
java.lang.IllegalArgumentException: Server has invalid Kerberos principal:
om/[email protected], expecting: OM/host1.dst.example.com@REALM,
while invoking $Proxy10.submitRequest over n [...]
```
**Cause:**
diff --git
a/versioned_docs/version-2.1.1/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
b/versioned_docs/version-2.1.1/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
index 528600c6df..6de09c29b5 100644
---
a/versioned_docs/version-2.1.1/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
+++
b/versioned_docs/version-2.1.1/05-administrator-guide/03-operations/04-disk-replacement/03-datanodes.md
@@ -130,8 +130,8 @@ Additional properties control disk health check behavior:
| Property | Default | Description |
|----------|---------|-------------|
-| `hdds.datanode.disk.check.io.test.count` | `3` | Number of IO tests required
to determine failure. Set to `0` to disable IO checks. |
-| `hdds.datanode.disk.check.io.failures.tolerated` | `1` | IO test failures
allowed before marking volume as failed |
+| `hdds.datanode.disk.check.io.test.count` | `3` | Number of I/O tests
required to determine failure. Set to `0` to disable I/O checks. |
+| `hdds.datanode.disk.check.io.failures.tolerated` | `1` | I/O test failures
allowed before marking volume as failed |
| `hdds.datanode.disk.check.io.file.size` | `100B` | Size of temporary file
used for I/O health checks |
| `hdds.datanode.disk.check.min.gap` | `10m` | Minimum time gap between
successive checks of the same volume |
| `hdds.datanode.disk.check.timeout` | `10m` | Maximum time allowed for a disk
check to complete |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
