From 43e61b13d680fd9739008ec1b7a81e7fabed8dd3 Mon Sep 17 00:00:00 2001 From: f64116045 Date: Tue, 25 Aug 2026 09:03:53 +0800 Subject: [PATCH] HDDS-16018. Update DNS-to-switch mapping documentation --- .../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.