priyeshkaratha commented on code in PR #365: URL: https://github.com/apache/ozone-site/pull/365#discussion_r2964135127
########## docs/05-administrator-guide/03-operations/09-observability/02-recon/03-recon-capacity-distribution.md: ########## @@ -0,0 +1,138 @@ +--- +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. Cluster Summary: The total physical disk view. +2. Service Summary: The logical state of Ozone data (Open, Committed, Pending Deletion). +3. 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 + +> Note: All metric values presented here are obtained from a representative sample cluster and are for reference purposes only. + +- **Total Capacity (2.2 TB)** + The combined capacity of all configured storage directories across all live Datanodes in the cluster. + It shows how much usable space is available after subtracting the reserved space from the file system capacity. + +- **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)** + 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. + +- **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. Review Comment: I think this section itself not required. Since info is already indicating that. -- 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]
