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 273f57643 HDDS-14921. [Auto] Update configuration documentation (#453)
273f57643 is described below
commit 273f576436972ec4f222006764458f4277c0c9b4
Author: asf-ci-deploy <[email protected]>
AuthorDate: Tue Jun 2 09:35:09 2026 +0200
HDDS-14921. [Auto] Update configuration documentation (#453)
---
docs/05-administrator-guide/02-configuration/99-appendix.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index a7e3ff803..522ed062e 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -748,6 +748,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `ozone.scm.network.topology.schema.file` | network-topology-default.xml |
`OZONE`, `MANAGEMENT` | The schema file defines the ozone network topology. We
currently support xml(default) and yaml format. Refer to the samples in the
topology awareness document for xml and yaml topology definition samples. |
| `ozone.scm.node.id` | | `OZONE`, `SCM`, `HA` | The ID of this SCM node. If
the SCM node ID is not configured it is determined automatically by matching
the local node's address with the configured address. If node ID is not
deterministic from the configuration, then it is set to the scmId from the SCM
version file. |
| `ozone.scm.nodes.EXAMPLESCMSERVICEID` | | `OZONE`, `SCM`, `HA` |
Comma-separated list of SCM node Ids for a given SCM service ID (eg.
EXAMPLESCMSERVICEID). The SCM service ID should be the value (one of the values
if there are multiple) set for the parameter `ozone.scm.service.ids`. Unique
identifiers for each SCM Node, delimited by commas. This will be used by SCMs
in HA setup to determine all the SCMs belonging to the same SCM in the cluster.
For example, if you used “scmService1” a [...]
+| `ozone.scm.pending.container.roll.interval` | 5m | `OZONE`, `SCM`,
`PERFORMANCE`, `MANAGEMENT` | The interval at which the two-window tumbling
bucket for pending container allocations rolls over per DataNode. Pending
containers that have not been confirmed within two intervals are automatically
aged out. Default is 5 minutes. |
| `ozone.scm.pipeline.allocated.timeout` | 5m | `OZONE`, `SCM`, `PIPELINE` |
Timeout for every pipeline to stay in ALLOCATED stage. When pipeline is
created, it should be at OPEN stage once pipeline report is successfully
received by SCM. If a pipeline stays at ALLOCATED longer than the specified
period of time, it should be scrubbed so that new pipeline can be created. This
timeout is for how long pipeline can stay at ALLOCATED stage until it gets
scrubbed. |
| `ozone.scm.pipeline.creation.auto.factor.one` | true | `OZONE`, `SCM`,
`PIPELINE` | If enabled, SCM will auto create RATIS factor ONE pipeline. |
| `ozone.scm.pipeline.creation.interval` | 120s | `OZONE`, `SCM`, `PIPELINE` |
SCM schedules a fixed interval job using the configured interval to create
pipelines. |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
