This is an automated email from the ASF dual-hosted git repository.

jojochuang 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 df04dd639c HDDS-16018. Update DNS-to-switch mapping documentation 
(#538)
df04dd639c is described below

commit df04dd639cdca82f5710c5f387e1bc86eac13825
Author: Shuo Huang <[email protected]>
AuthorDate: Tue Sep 29 16:01:37 2026 +0800

    HDDS-16018. Update DNS-to-switch mapping documentation (#538)
---
 .../02-configuration/04-performance/02-topology.md                      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/docs/05-administrator-guide/02-configuration/04-performance/02-topology.md 
b/docs/05-administrator-guide/02-configuration/04-performance/02-topology.md
index 4111053d06..f0c56ed4cf 100644
--- a/docs/05-administrator-guide/02-configuration/04-performance/02-topology.md
+++ b/docs/05-administrator-guide/02-configuration/04-performance/02-topology.md
@@ -22,7 +22,7 @@ See the [page about 
Containers](../../../core-concepts/replication/storage-conta
 
 ## Configuring Topology Hierarchy
 
-Ozone determines Datanode network locations (e.g., racks) using Hadoop's rack 
awareness, configured via `net.topology.node.switch.mapping.impl` in 
`ozone-site.xml`. This key specifies a 
`org.apache.hadoop.net.CachedDNSToSwitchMapping` implementation. [1]
+Ozone determines Datanode network locations (e.g., racks) using Hadoop's rack 
awareness, configured via `net.topology.node.switch.mapping.impl` in 
`ozone-site.xml`. The value of this key is the class name of an implementation 
of `org.apache.hadoop.net.DNSToSwitchMapping`. [1]
 
 :::note
 Both Ozone Manager (OM) and Storage Container Manager (SCM) use network 
topology information. It is critical to maintain a consistent topology 
assignment across all OM and SCM instances in the cluster.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to