ArafatKhan2198 commented on PR #6508: URL: https://github.com/apache/ozone/pull/6508#issuecomment-2066370299
> Thanks @ArafatKhan2198 for the fix, @devmadhuu for the review. @adoroszlai `ClusterStateEndpoint` in Recon requests the cluster-wide storage statistics, the `ReconNodeManager` aggregates the individual Datanode statistics to calculate the `total capacity`, `used space`, and `remaining space` for the entire cluster. The `ReconNodeManager` exposes methods like `getStats()`, which returns an object (e.g., SCMNodeStat) containing the aggregated storage statistics. The ClusterStateEndpoint then uses these aggregated statistics to create the `DatanodeStorageReport` and include it in the ClusterStateResponse. So, in summary, the Recon component gets the storage information from the periodic heartbeat messages sent by the individual Datanodes in the cluster. The ReconNodeManager aggregates these individual Datanode statistics to provide the cluster-wide storage information to other components like the ClusterStateEndpoint. This is my understanding from the code. We do not store the space in any of the DB's in recon (Derby or Rocks) @devmadhuu @adoroszlai please correct me if I am making a wrong assumption anywhere. -- 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]
