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 50303e06d HDDS-15531. [Auto] Update configuration documentation (#464)
50303e06d is described below
commit 50303e06d7be19dd4ddbbaeba540baa4d2b8312b
Author: asf-ci-deploy <[email protected]>
AuthorDate: Tue Jun 16 07:07:56 2026 +0200
HDDS-15531. [Auto] Update configuration documentation (#464)
---
docs/05-administrator-guide/02-configuration/99-appendix.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index 2c13ef98e..57031a5ce 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -270,6 +270,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `hdds.scm.safemode.log.interval` | 1m | `HDDS`, `SCM`, `OPERATION` |
Interval at which SCM logs safemode status while SCM is in safemode. Default is
1 minute. |
| `hdds.scm.safemode.min.datanode` | 3 | `HDDS`, `SCM`, `OPERATION` | Minimum
DataNodes which should be registered to get SCM out of safe mode. |
| `hdds.scm.safemode.pipeline.creation` | true | `HDDS`, `SCM`, `OPERATION` |
Boolean value to enable background pipeline creation in SCM safe mode. |
+| `hdds.scm.safemode.rule.refresh.interval` | 5s | `HDDS`, `SCM`, `OPERATION`
| Refresh interval in SCM Safemode. |
| `hdds.scm.safemode.threshold.pct` | 0.99 | `HDDS`, `SCM`, `OPERATION` | % of
containers which should have at least one reported replica before SCM comes out
of safe mode. |
| `hdds.scm.unknown-container.action` | WARN | `SCM`, `MANAGEMENT` | The
action taken by SCM to process unknown containers that reported by Datanodes.
The default action is just logging container not found warning, another
available action is DELETE action. These unknown containers will be deleted
under this action way. |
| `hdds.scm.wait.time.after.safemode.exit` | 5m | `HDDS`, `SCM`, `OPERATION` |
After exiting safemode, wait for configured interval of time to start
replication monitor and cleanup activities of unhealthy pipelines. |
@@ -362,6 +363,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `ozone.client.elastic.byte.buffer.pool.max.size` | 16GB | `OZONE`, `CLIENT`
| The maximum total size of buffers that can be cached in the client-side
ByteBufferPool. This pool is used heavily during EC read and write operations.
Setting a limit prevents unbounded memory growth in long-lived rpc clients like
the S3 Gateway. Once this limit is reached, used buffers are not put back to
the pool and will be garbage collected. |
| `ozone.client.exclude.nodes.expiry.time` | 600000 | `CLIENT` | Time after
which an excluded node is reconsidered for writes. If the value is zero, the
node is excluded for the life of the client |
| `ozone.client.failover.max.attempts` | 500 | | Expert only. Ozone RpcClient
attempts talking to each OzoneManager ipc.client.connect.max.retries (default =
10) number of times before failing over to another OzoneManager, if available.
This parameter represents the number of times per request the client will
failover before giving up. This value is kept high so that client does not give
up trying to connect to OMs easily. |
+| `ozone.client.failover.resolve-needed` | false | `OZONE`, `CLIENT`, `OM`,
`SCM`, `HA` | When true, RPC clients (DN heartbeat, OM client, SCM client)
re-resolve cached hostnames on connection-class failures (ConnectException,
SocketTimeoutException, NoRouteToHostException, UnknownHostException,
EOFException, SocketException) and rebuild the proxy if the resolved IP has
changed. Set to true in environments where server pod IPs may change while DNS
names remain stable, such as Kubernetes. [...]
| `ozone.client.follower.read.default.consistency` |
LINEARIZABLE_ALLOW_FOLLOWER | | The default consistency when client enables
follower read. Currently, the supported follower read consistency are
LINEARIZABLE_ALLOW_FOLLOWER and LOCAL_LEASE The default value is
LINEARIZABLE_ALLOW_FOLLOWER to preserve the same strong consistency behavior
when switching from leader-only read to follower read. |
| `ozone.client.follower.read.enabled` | false | | Enable client to read from
OM followers. If false, all client requests are sent to the OM leader. |
| `ozone.client.fs.default.bucket.layout` | FILE_SYSTEM_OPTIMIZED | `CLIENT` |
Default bucket layout value used when buckets are created using OFS. Supported
values are LEGACY and FILE_SYSTEM_OPTIMIZED. FILE_SYSTEM_OPTIMIZED: This layout
allows the bucket to support atomic rename/delete operations and also allows
interoperability between S3 and FS APIs. Keys written via S3 API with a '/'
delimiter will create intermediate directories. |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
