priyeshkaratha opened a new pull request, #8995: URL: https://github.com/apache/ozone/pull/8995
## What changes were proposed in this pull request? Here the pending deletion bytes are calculated and updated in the BlockDeletionService metrics, which are then exposed via JMX. This allows for direct access to these metrics by monitoring tools. The primary disadvantage of this approach is the introduction of a dependency on JMX. While this might be a minor concern in some deployments, it's worth noting the additional dependency. This method avoids the unnecessary data transfer to SCM and the associated processing overhead in DN while iterating and calculating pending deletion from the container data list that is present with the Storage Report approach. ## What is the link to the Apache JIRA HDDS-13465 ## How was this patch tested? Manually tested using Recon API. -- 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]
