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 d74e0d67e HDDS-15313. [Auto] Update configuration documentation (#466)
d74e0d67e is described below
commit d74e0d67ea69a2d4578b12ebc2b7e8fb2cfbeeec
Author: asf-ci-deploy <[email protected]>
AuthorDate: Sun Jun 28 12:24:09 2026 +0200
HDDS-15313. [Auto] Update configuration documentation (#466)
---
docs/05-administrator-guide/02-configuration/99-appendix.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index 57031a5ce..7452d57c1 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -553,9 +553,9 @@ This page provides a comprehensive overview of the
configuration keys available
| `ozone.om.snapshot.diff.disable.native.libs` | false | `OZONE`, `OM` | Flag
to perform snapshot diff without using native libs(can be slow). |
| `ozone.om.snapshot.diff.job.default.wait.time` | 1m | `OZONE`, `OM` |
Default wait time returned to client to wait before retrying snap diff request.
Uses millisecond by default when no time unit is specified. |
| `ozone.om.snapshot.diff.job.report.persistent.time` | 7d | `OZONE`, `OM` |
Maximum time a successful snapshot diff job and its report will be persisted.
Uses millisecond by default when no time unit is specified. |
-| `ozone.om.snapshot.diff.max.allowed.keys.changed.per.job` | 10000000 |
`OZONE`, `OM` | Max numbers of keys changed allowed for a snapshot diff job. |
+| `ozone.om.snapshot.diff.max.allowed.keys.changed.per.job` | 1000000000 |
`OZONE`, `OM` | Max numbers of keys changed allowed for a snapshot diff job. |
| `ozone.om.snapshot.diff.max.jobs.purge.per.task` | 100 | `OZONE`, `OM` |
Maximum number of snapshot diff jobs to be purged per snapDiff clean up run. |
-| `ozone.om.snapshot.diff.max.page.size` | 1000 | `OZONE`, `OM` | Maximum
number of entries to be returned in a single page of snap diff report. |
+| `ozone.om.snapshot.diff.max.page.size` | 5000 | `OZONE`, `OM` | Maximum
number of entries to be returned in a single page of snap diff report. |
| `ozone.om.snapshot.diff.thread.pool.size` | 10 | `OZONE`, `OM` | Maximum
numbers of concurrent snapshot diff jobs are allowed. |
| `ozone.om.snapshot.directory.metrics.update.interval` | 5m | `OZONE`, `OM` |
Time interval used to update the space consumption stats of the Ozone Manager
snapshot directories. Background thread periodically calculates and updates
these stats. Unit could be defined with postfix (ns,ms,s,m,h,d) |
| `ozone.om.snapshot.force.full.diff` | false | `OZONE`, `OM` | Flag to always
perform full snapshot diff (can be slow) without using the optimised compaction
DAG. |
@@ -755,6 +755,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `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. |
+| `ozone.scm.pipeline.creation.ratis.three` | true | `OZONE`, `SCM`,
`PIPELINE` | When true, SCM creates RATIS/THREE pipelines in the background and
requires them during safemode. Applies only when the cluster default
replication type is EC. For RATIS-default clusters this flag has no effect. |
| `ozone.scm.pipeline.destroy.timeout` | 66s | `OZONE`, `SCM`, `PIPELINE` |
Once a pipeline is closed, SCM should wait for the above configured time before
destroying a pipeline. |
| `ozone.scm.pipeline.leader-choose.policy` |
org.apache.hadoop.hdds.scm.pipeline.leader.choose.algorithms.MinLeaderCountChoosePolicy
| `OZONE`, `SCM`, `PIPELINE` | The policy used for choosing desired leader for
pipeline creation. There are two policies supporting now:
DefaultLeaderChoosePolicy, MinLeaderCountChoosePolicy.
org.apache.hadoop.hdds.scm.pipeline.leader.choose.algorithms.DefaultLeaderChoosePolicy
implements a policy that choose leader without depending on priority.
org.apach [...]
| `ozone.scm.pipeline.owner.container.count` | 3 | `OZONE`, `SCM`, `PIPELINE`
| Number of containers per owner per disk in a pipeline. |
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
