Gargi-jais11 commented on code in PR #365: URL: https://github.com/apache/ozone-site/pull/365#discussion_r2946089942
########## 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. Review Comment: The doc says "non-Ozone files / OS files / other Hadoop services." Checking the description for this in UI says it is actually Ozone's own overhead files (RocksDB, config, logs) — not external processes. These are opposite meanings. A user reading the doc will look for non-Ozone processes when the real cause is Ozone's own metadata. Let's keep the same description. ``` This is the space occupied by other Ozone related files but not actual data stored by Ozone. This may include things like logs, configuration files, Rocks DB files etc. ``` Because the non-ozone used space as far as I know is counted as part of reserved space which is already subtracted from the total capacity. -- 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]
