sarvekshayr commented on code in PR #226:
URL: https://github.com/apache/ozone-site/pull/226#discussion_r2697729867
##########
docs/05-administrator-guide/02-configuration/04-performance/02-topology.md:
##########
@@ -165,22 +171,22 @@ For Erasure Coded (EC) containers, SCM employs a
specialized placement policy to
</property>
```
-- **Behavior:** If the number of available racks is less than the number of
blocks in the EC group, the policy will start placing more than one block on
the same rack, while trying to keep the distribution as even as possible.
-- **Limitations:** Similar to `SCMContainerPlacementRackAware`, this policy is
designed for single-layer rack topologies (e.g., `/rack/node`) and is not
recommended for multi-layer hierarchies.
+ - **Behavior:** If the number of available racks is less than the number of
blocks in the EC group, the policy will start placing more than one block on
the same rack, while trying to keep the distribution as even as possible.
+ - **Limitations:** Similar to `SCMContainerPlacementRackAware`, this policy
is designed for single-layer rack topologies (e.g., `/rack/node`) and is not
recommended for multi-layer hierarchies.
## Optimizing Read Paths
-Enable by setting `ozone.network.topology.aware.read` to `true` in
`ozone-site.xml`. [1]
+This feature, enabled by default since Ozone 1.4.0 (HDDS-8300), directs
clients to read from the topologically closest Datanodes for replicated data,
reducing latency and cross-rack traffic. It is recommended to keep this enabled
when you have an accurate topology configuration.
Review Comment:
Let's link [HDDS-8300](https://issues.apache.org/jira/browse/HDDS-8300).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
