This is an automated email from the ASF dual-hosted git repository.
adoroszlai 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 c3e2d43ae HDDS-14925. [Auto] Update configuration documentation (#426)
c3e2d43ae is described below
commit c3e2d43ae5bb707e72cd90eef14098707ebdb579
Author: asf-ci-deploy <[email protected]>
AuthorDate: Tue May 19 18:40:39 2026 +0200
HDDS-14925. [Auto] Update configuration documentation (#426)
---
docs/05-administrator-guide/02-configuration/99-appendix.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index 46c365b33..21846a1d4 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -183,8 +183,9 @@ This page provides a comprehensive overview of the
configuration keys available
| `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. |
| `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` | This determines the free space to be used for closing
containers When the difference between volume capacity and used reaches this
number, containers that reside on this volume will be closed and no new
containers would be allocated on this volume. Max of min.free.space and
min.free.space.percent will be used as final value. |
-| `hdds.datanode.volume.min.free.space.percent` | 0.02 | `OZONE`, `CONTAINER`,
`STORAGE`, `MANAGEMENT` | This determines the free space percent to be used for
closing containers When the difference between volume capacity and used reaches
(free.space.percent of volume capacity), containers that reside on this volume
will be closed and no new containers would be allocated on this volume. Max of
min.free.space or min.free.space.percent will be used as final value. |
+| `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. |
+| `hdds.datanode.volume.min.free.space.percent` | 0.02 | `OZONE`, `CONTAINER`,
`STORAGE`, `MANAGEMENT` | Minimum fraction of volume capacity reported to SCM
as freeSpaceToSpare (heartbeat / storage reports). Local write rejection uses
`hdds.datanode.volume.min.free.space.hard.limit.percent` instead. The soft band
is the gap between these two (e.g. 2000GB disk: 2% = 40GB reported vs 1.5% =
30GB hard → 10GB band) where the DN may send close-container actions while
writes still succeed. |
| `hdds.datanode.wait.on.all.followers` | false | `DATANODE` | Defines whether
the leader datanode will wait for bothfollowers to catch up before removing the
stateMachineData from the cache. |
| `hdds.db.profile` | DISK | `OZONE`, `OM`, `PERFORMANCE` | This property
allows user to pick a configuration that tunes the RocksDB settings for the
hardware it is running on. Right now, we have SSD and DISK as profile options. |
| `hdds.grpc.tls.ciphers` | | `OZONE`, `HDDS`, `SECURITY`, `TLS`,
`CRYPTO_COMPLIANCE` | Comma-separated list of TLS cipher suites for gRPC server
endpoints (e.g. "TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256"). When empty,
the TLS provider's defaults are used. Applies to server endpoints only; clients
are not restricted. |
@@ -349,7 +350,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `ozone.client.connection.timeout` | 5000ms | `OZONE`, `PERFORMANCE`,
`CLIENT` | Connection timeout for Ozone client in milliseconds. |
| `ozone.client.datastream.buffer.flush.size` | 16MB | `CLIENT` | The boundary
at which putBlock is executed |
| `ozone.client.datastream.min.packet.size` | 1MB | `CLIENT` | The maximum
size of the ByteBuffer (used via ratis streaming) |
-| `ozone.client.datastream.pipeline.mode` | true | `CLIENT` | Streaming write
support both pipeline mode(datanode1->datanode2->datanode3) and star
mode(datanode1->datanode2, datanode1->datanode3). By default we use pipeline
mode. |
+| `ozone.client.datastream.pipeline.mode` | true | `CLIENT` | Streaming write
support both pipeline mode(datanode1->datanode2->datanode3) and star
mode(datanode1->datanode2, datanode1->datanode3). By default we use
pipeline mode. |
| `ozone.client.datastream.sync.size` | 0B | `CLIENT` | The minimum size of
written data before forcing the datanodes in the pipeline to flush the pending
data to underlying storage. If set to zero or negative, the client will not
force the datanodes to flush. |
| `ozone.client.datastream.window.size` | 64MB | `CLIENT` | Maximum size of
BufferList(used for retry) size per BlockDataStreamOutput instance |
| `ozone.client.ec.grpc.retries.enabled` | true | `CLIENT` | To enable Grpc
client retries for EC. |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
