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 a3a639a0c HDDS-15203. [Auto] Update configuration documentation (#423)
a3a639a0c is described below

commit a3a639a0cc5579141a87bb03f24c199973f43bdc
Author: asf-ci-deploy <[email protected]>
AuthorDate: Sun May 10 20:06:57 2026 +0200

    HDDS-15203. [Auto] Update configuration documentation (#423)
---
 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 c23842181..b21349f7e 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -496,7 +496,7 @@ This page provides a comprehensive overview of the 
configuration keys available
 | `ozone.om.multitenancy.enabled` | false | `OZONE`, `OM` | Enable S3 
Multi-Tenancy. If disabled, all S3 multi-tenancy requests are rejected. |
 | `ozone.om.multitenancy.ranger.sync.interval` | 10m | `OZONE`, `OM` | 
Determines how often the Multi-Tenancy Ranger background sync thread service 
should run. Background thread periodically checks Ranger policies and roles 
created by Multi-Tenancy feature. And overwrites them if obvious discrepancies 
are detected. Value should be set with a unit suffix (ns,ms,s,m,h,d) |
 | `ozone.om.multitenancy.ranger.sync.timeout` | 10s | `OZONE`, `OM` | The 
timeout for each Multi-Tenancy Ranger background sync thread run. If the 
timeout has been reached, a warning message will be logged. |
-| `ozone.om.namespace.s3.strict` | true | `OZONE`, `OM` | Ozone namespace 
should follow S3 naming rule by default. However this parameter allows the 
namespace to support non-S3 compatible characters. |
+| `ozone.om.namespace.s3.strict` | true | `OZONE`, `OM` | When `true` (the 
default), volume and bucket names follow strict S3 naming rules. When `false`, 
S3 rules still apply except that underscore (`_`) is additionally allowed in 
volume and bucket names; no other non-S3 characters are permitted. |
 | `ozone.om.network.topology.refresh.duration` | 1h | `SCM`, `OZONE`, `OM` | 
The duration at which we periodically fetch the updated network topology 
cluster tree from SCM. |
 | `ozone.om.node.id` |  | `OM`, `HA` | The ID of this OM node. If the OM 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 default node id - om1. |
 | `ozone.om.nodes.EXAMPLEOMSERVICEID` |  | `OM`, `HA` | Comma-separated list 
of OM node Ids for a given OM service ID (eg. EXAMPLEOMSERVICEID). The OM 
service ID should be the value (one of the values if there are multiple) set 
for the parameter `ozone.om.service.ids`. Decommissioned nodes (represented by 
node Ids in ozone.om.decommissioned.nodes config list) will be ignored and not 
included in the OM HA setup even if added to this list. Unique identifiers for 
each OM Node, delimited by  [...]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to