This is an automated email from the ASF dual-hosted git repository.
weichiu pushed a commit to branch HDDS-9225-website-v2
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/HDDS-9225-website-v2 by this
push:
new 3862a33f9 HDDS-11928. [Website v2] [Docs] [Core Concepts] Storage
Containers. (#110)
3862a33f9 is described below
commit 3862a33f92ee1ec338c0f833d8589d63fcadd95a
Author: Wei-Chiu Chuang <[email protected]>
AuthorDate: Fri Jan 23 09:15:16 2026 -0800
HDDS-11928. [Website v2] [Docs] [Core Concepts] Storage Containers. (#110)
Co-authored-by: Siyao Meng <[email protected]>
---
.../02-replication/01-storage-containers.md | 37 +++++++++++++++++++--
.../02-replication/ContainerMetadata.png | Bin 0 -> 98493 bytes
.../03-core-concepts/02-replication/Containers.png | Bin 0 -> 24775 bytes
.../02-configuration/03-security/02-kerberos.md | 2 +-
4 files changed, 36 insertions(+), 3 deletions(-)
diff --git a/docs/03-core-concepts/02-replication/01-storage-containers.md
b/docs/03-core-concepts/02-replication/01-storage-containers.md
index ff06a2318..35ae271da 100644
--- a/docs/03-core-concepts/02-replication/01-storage-containers.md
+++ b/docs/03-core-concepts/02-replication/01-storage-containers.md
@@ -1,5 +1,38 @@
+<!---
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
# Storage Containers
-**TODO:** File a subtask under
[HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this
page or section.
+Storage Containers, or Containers (not to be confused with Docker containers)
are the fundamental replication unit of Ozone, they are managed by the Storage
Container Manager (SCM) service.
+
+Containers are big binary units (5GB by default) which can contain multiple
blocks:
+
+
+
+Blocks are local information and not managed by SCM. Therefore even if
billions of small files are created in the system (which means billions of
blocks are created), only of the status of the containers will be reported by
the Datanodes and containers will be replicated.
+When Ozone Manager requests a new Block allocation from the SCM, SCM will
identify the suitable container and generate a block id which contains
`ContainerId` + `LocalId`. Client will connect to the Datanode which stores the
Container, and Datanode can manage the separated block based on the `LocalId`.
+
+## Open vs. Closed containers
+
+When a container is created it starts in an OPEN state. When it's full (~5GB
data is written), container will be closed and becomes a CLOSED container.
+
+The fundamental differences between OPEN and CLOSED containers:
-Provide a high level summary of storage containers and their purpose.
Technically this is just for context and deep understanding is not required by
most users of the system. The System Internals section of the docs will have
much more details on containers.
+| OPEN | CLOSED |
+|-----------------------------------|-----------------------------------------|
+| mutable | immutable |
+| replicated with RAFT (Ratis) | Replicated with async container copy |
+| Raft leader is used to READ / WRITE | All the nodes can be used to READ |
diff --git a/docs/03-core-concepts/02-replication/ContainerMetadata.png
b/docs/03-core-concepts/02-replication/ContainerMetadata.png
new file mode 100644
index 000000000..48bd1c43c
Binary files /dev/null and
b/docs/03-core-concepts/02-replication/ContainerMetadata.png differ
diff --git a/docs/03-core-concepts/02-replication/Containers.png
b/docs/03-core-concepts/02-replication/Containers.png
new file mode 100644
index 000000000..3d2df0f31
Binary files /dev/null and
b/docs/03-core-concepts/02-replication/Containers.png differ
diff --git
a/docs/05-administrator-guide/02-configuration/03-security/02-kerberos.md
b/docs/05-administrator-guide/02-configuration/03-security/02-kerberos.md
index f6ea1499a..3d087ed69 100644
--- a/docs/05-administrator-guide/02-configuration/03-security/02-kerberos.md
+++ b/docs/05-administrator-guide/02-configuration/03-security/02-kerberos.md
@@ -25,7 +25,7 @@ SCM requires two Kerberos principals, and the corresponding
key tab files for bo
| `hdds.scm.http.auth.kerberos.keytab` | The keytab file used by SCM HTTP
server to login as its service principal if SPNEGO is enabled for SCM HTTP
server. |
:::note
-For general configuration on enabling Kerberos based SPNEGO authentication for
HTTP web-consoles, refer to [Configuring
HTTPS](/docs/05-administrator-guide/02-configuration/03-security/03-https.md).
+For general configuration on enabling Kerberos based SPNEGO authentication for
HTTP web-consoles, refer to [Configuring HTTP authentication using Kerberos
SPNEGO](/docs/05-administrator-guide/02-configuration/03-security/03-https.md).
:::
## Ozone Manager
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
