Gargi-jais11 commented on code in PR #365:
URL: https://github.com/apache/ozone-site/pull/365#discussion_r2946017218
##########
docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md:
##########
@@ -0,0 +1,132 @@
+---
+sidebar_label: Cluster Capacity User Guide
+---
+# Cluster Capacity User Guide
+
+This page is the central place for understanding storage distribution across
the Ozone cluster.
+It moves from a high-level physical view to logical service usage, and down to
individual node diagnostics.
+Use this guide to understand exactly where your storage capacity is going.
+
+## Dashboard Layout Overview
+
+The Cluster Capacity page is organized logically from top to bottom,
increasing in granularity:
+
+1. Header & Controls: Global settings and refresh rates.
+2. Cluster Summary: The total physical disk view.
+3. Service Summary: The logical state of Ozone data (Open, Committed, Pending
Deletion).
+4. Pending Deletion & Datanode Insights: Deep dives into data deletion life
cycles and individual node performance.
+
+---
+
+## Cluster (Physical Capacity)
+
+
+The **Cluster** widget provides a high-level summary of the total physical
storage managed by Ozone Datanodes. It helps you distinguish between space used
by Ozone and space taken by other processes on the underlying hardware.
+
+### Metric Definitions
+
+- **Total Capacity (2.2 TB)**
+ The combined capacity of all configured storage directories across all live
Datanodes in the cluster.
+
+- **Ozone Used Space (437.3 GB)**
+ Physical space currently occupied by replicated Ozone blocks.
+ > Note: This accounts for the replication factor (e.g., a 100 GB key with 3x
replication uses 300 GB of physical space).
+
+- **Other Used Space (482.5 GB)**
+ Space on the disks that is occupied by non-Ozone files. This includes OS
files, system logs, temp directories, or other Hadoop services running on the
same hardware.
+
+- **Container Pre-allocated (0 B)**
+ Space reserved for open containers that have been allocated to clients but
have not yet been written to. This ensures space is available when needed.
+
+- **Remaining Space (1.3 TB)**
+ The actual amount of unused physical disk space available for new Ozone data
or other files.
+
+> 💡 **Administrator Tip:**
+> Monitor **Other Used Space**. If this value is consistently high, it may
indicate that non-Ozone processes are competing for disk space, which could
lead to capacity issues for your Ozone data.
+
+---
+
+## Service (Logical Capacity)
+
+
+The **Service** widget transitions from the physical view to the logical view.
It breaks down the **Ozone Used Space** based on the state of the data keys
within the Ozone architecture.
Review Comment:
Similar, first description then image.
```suggestion
The **Service** widget transitions from the physical view to the logical
view. It breaks down the **Ozone Used Space** based on the state of the data
keys within the Ozone architecture.
```
##########
docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md:
##########
@@ -0,0 +1,132 @@
+---
+sidebar_label: Cluster Capacity User Guide
+---
+# Cluster Capacity User Guide
+
+This page is the central place for understanding storage distribution across
the Ozone cluster.
+It moves from a high-level physical view to logical service usage, and down to
individual node diagnostics.
+Use this guide to understand exactly where your storage capacity is going.
+
+## Dashboard Layout Overview
+
+The Cluster Capacity page is organized logically from top to bottom,
increasing in granularity:
+
+1. Header & Controls: Global settings and refresh rates.
Review Comment:
Please provide what does this mean or you can add the UI snapshot for this
part explaining.
##########
docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md:
##########
@@ -0,0 +1,132 @@
+---
+sidebar_label: Cluster Capacity User Guide
+---
+# Cluster Capacity User Guide
+
+This page is the central place for understanding storage distribution across
the Ozone cluster.
+It moves from a high-level physical view to logical service usage, and down to
individual node diagnostics.
+Use this guide to understand exactly where your storage capacity is going.
+
+## Dashboard Layout Overview
+
+The Cluster Capacity page is organized logically from top to bottom,
increasing in granularity:
+
+1. Header & Controls: Global settings and refresh rates.
+2. Cluster Summary: The total physical disk view.
+3. Service Summary: The logical state of Ozone data (Open, Committed, Pending
Deletion).
+4. Pending Deletion & Datanode Insights: Deep dives into data deletion life
cycles and individual node performance.
+
+---
+
+## Cluster (Physical Capacity)
+
+
+The **Cluster** widget provides a high-level summary of the total physical
storage managed by Ozone Datanodes. It helps you distinguish between space used
by Ozone and space taken by other processes on the underlying hardware.
Review Comment:
Let's first give description and then show the sample image.
```suggestion
The **Cluster** widget provides a high-level summary of the total physical
storage managed by Ozone Datanodes. It helps you distinguish between space used
by Ozone and space taken by other processes on the underlying hardware.
```
##########
docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md:
##########
@@ -0,0 +1,132 @@
+---
+sidebar_label: Cluster Capacity User Guide
+---
+# Cluster Capacity User Guide
+
+This page is the central place for understanding storage distribution across
the Ozone cluster.
+It moves from a high-level physical view to logical service usage, and down to
individual node diagnostics.
+Use this guide to understand exactly where your storage capacity is going.
+
+## Dashboard Layout Overview
+
+The Cluster Capacity page is organized logically from top to bottom,
increasing in granularity:
+
+1. Header & Controls: Global settings and refresh rates.
+2. Cluster Summary: The total physical disk view.
+3. Service Summary: The logical state of Ozone data (Open, Committed, Pending
Deletion).
+4. Pending Deletion & Datanode Insights: Deep dives into data deletion life
cycles and individual node performance.
+
+---
+
+## Cluster (Physical Capacity)
+
+
+The **Cluster** widget provides a high-level summary of the total physical
storage managed by Ozone Datanodes. It helps you distinguish between space used
by Ozone and space taken by other processes on the underlying hardware.
+
+### Metric Definitions
+
+- **Total Capacity (2.2 TB)**
+ The combined capacity of all configured storage directories across all live
Datanodes in the cluster.
Review Comment:
Please mention that it shows the combined capacity of physical disks after
removing the reserved space and you can mention by default what's the du
reserved space.
##########
docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md:
##########
@@ -0,0 +1,132 @@
+---
+sidebar_label: Cluster Capacity User Guide
+---
+# Cluster Capacity User Guide
+
+This page is the central place for understanding storage distribution across
the Ozone cluster.
+It moves from a high-level physical view to logical service usage, and down to
individual node diagnostics.
+Use this guide to understand exactly where your storage capacity is going.
+
+## Dashboard Layout Overview
+
+The Cluster Capacity page is organized logically from top to bottom,
increasing in granularity:
+
+1. Header & Controls: Global settings and refresh rates.
+2. Cluster Summary: The total physical disk view.
+3. Service Summary: The logical state of Ozone data (Open, Committed, Pending
Deletion).
+4. Pending Deletion & Datanode Insights: Deep dives into data deletion life
cycles and individual node performance.
+
+---
+
+## Cluster (Physical Capacity)
+
+
+The **Cluster** widget provides a high-level summary of the total physical
storage managed by Ozone Datanodes. It helps you distinguish between space used
by Ozone and space taken by other processes on the underlying hardware.
+
+### Metric Definitions
Review Comment:
Here, may be you can add one liner refering to the above image these are the
metric definitions.
This will give first time recon user an impression that the values shown for
each metrics are not hard coded one, its just for explanation.
##########
docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md:
##########
@@ -0,0 +1,132 @@
+---
+sidebar_label: Cluster Capacity User Guide
+---
+# Cluster Capacity User Guide
+
+This page is the central place for understanding storage distribution across
the Ozone cluster.
+It moves from a high-level physical view to logical service usage, and down to
individual node diagnostics.
+Use this guide to understand exactly where your storage capacity is going.
+
+## Dashboard Layout Overview
+
+The Cluster Capacity page is organized logically from top to bottom,
increasing in granularity:
+
+1. Header & Controls: Global settings and refresh rates.
+2. Cluster Summary: The total physical disk view.
+3. Service Summary: The logical state of Ozone data (Open, Committed, Pending
Deletion).
+4. Pending Deletion & Datanode Insights: Deep dives into data deletion life
cycles and individual node performance.
+
+---
+
+## Cluster (Physical Capacity)
+
+
+The **Cluster** widget provides a high-level summary of the total physical
storage managed by Ozone Datanodes. It helps you distinguish between space used
by Ozone and space taken by other processes on the underlying hardware.
+
+### Metric Definitions
+
+- **Total Capacity (2.2 TB)**
+ The combined capacity of all configured storage directories across all live
Datanodes in the cluster.
+
+- **Ozone Used Space (437.3 GB)**
+ Physical space currently occupied by replicated Ozone blocks.
+ > Note: This accounts for the replication factor (e.g., a 100 GB key with 3x
replication uses 300 GB of physical space).
+
+- **Other Used Space (482.5 GB)**
+ Space on the disks that is occupied by non-Ozone files. This includes OS
files, system logs, temp directories, or other Hadoop services running on the
same hardware.
+
+- **Container Pre-allocated (0 B)**
+ Space reserved for open containers that have been allocated to clients but
have not yet been written to. This ensures space is available when needed.
Review Comment:
```suggestion
- **Container Pre-allocated (0 B)**
Space reserved for open containers that have been allocated to clients but
have not yet been written to ( basically committed bytes). This ensures space
is available when needed.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
