This is an automated email from the ASF dual-hosted git repository.
asf-ci-deploy pushed a commit to branch automated-config-doc-update
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
commit ecbae07cc2f6325ab5e25bdf02650ad1f7e74b26
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Jul 28 16:03:47 2026 +0000
HDDS-15922. [Auto] Update configuration documentation from ozone
d501066b60fdb64b5ea415282285ea46c5970871
---
docs/05-administrator-guide/02-configuration/99-appendix.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index be2907a8e8..0fcff71746 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -181,7 +181,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `hdds.datanode.slow.op.warning.threshold` | 500ms | `OZONE`, `DATANODE`,
`PERFORMANCE` | Thresholds for printing slow-operation audit logs. |
| `hdds.datanode.storage.utilization.critical.threshold` | 0.95 | `OZONE`,
`SCM`, `MANAGEMENT` | If a datanode overall storage utilization exceeds more
than this value, the datanode will be marked out of space. |
| `hdds.datanode.storage.utilization.warning.threshold` | 0.75 | `OZONE`,
`SCM`, `MANAGEMENT` | If a datanode overall storage utilization exceeds more
than this value, a warning will be logged while processing the nodeReport in
SCM. |
-| `hdds.datanode.use.datanode.hostname` | false | `OZONE`, `DATANODE` |
Whether Datanodes should use Datanode hostnames when connecting to other
Datanodes for data transfer. See [Troubleshooting client
connectivity](../../troubleshooting/client-connectivity). |
+| `hdds.datanode.use.datanode.hostname` | false | `OZONE`, `DATANODE` |
Whether Datanodes should use Datanode hostnames when connecting to other
Datanodes for data transfer. |
| `hdds.datanode.volume.choosing.policy` |
org.apache.hadoop.ozone.container.common.volume.CapacityVolumeChoosingPolicy |
`OZONE`, `CONTAINER`, `STORAGE`, `MANAGEMENT` | The class name of the policy
for choosing volumes in the list of directories. Defaults to
org.apache.hadoop.ozone.container.common.volume.CapacityVolumeChoosingPolicy.
This volume choosing policy randomly chooses two volumes with remaining space
and then picks the one with lower utilization. |
| `hdds.datanode.volume.min.free.space` | -1 | `OZONE`, `CONTAINER`,
`STORAGE`, `MANAGEMENT` | Minimum free space (bytes) applied together with
min.free.space.percent (reported to SCM in heartbeat as freeSpaceToSpare) and
min.free.space.hard.limit.percent (local write enforcement). The effective
value for each tier is max(this bytes, capacity * ratio). |
| `hdds.datanode.volume.min.free.space.hard.limit.percent` | 0.015 | `OZONE`,
`CONTAINER`, `STORAGE`, `MANAGEMENT` | Minimum fraction of volume capacity
reserved for local enforcement: writes fail when available space would drop
below max(this ratio * capacity, `hdds.datanode.volume.min.free.space`). Should
be <= min.free.space.percent so SCM can plan for a larger headroom than the
DN enforces locally. |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
