[
https://issues.apache.org/jira/browse/HDDS-14625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyesh K updated HDDS-14625:
-----------------------------
Summary: SCM Pending Deletion should reflect the actual replicated space
consumed in the cluster. (was: SCM Pending Deletion should report replicated
block size instead of block size)
> SCM Pending Deletion should reflect the actual replicated space consumed in
> the cluster.
> ----------------------------------------------------------------------------------------
>
> Key: HDDS-14625
> URL: https://issues.apache.org/jira/browse/HDDS-14625
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Recon
> Reporter: Priyesh K
> Assignee: Priyesh K
> Priority: Major
>
> In the Cluster Capacity UI, the *Pending Deletion* card is currently
> displaying the _unreplicated_ size. However, this does not accurately reflect
> the actual space being held by SCM tasks.
> The intention is to show the *total space occupied across the cluster* by
> blocks that are pending deletion. Since data is replicated, the space impact
> is based on the {*}replicated size{*}, not the original key size.
> For example, if a 100 MB key is deleted and the replication factor is 3, SCM
> is actually holding *300 MB* (100 MB × 3) worth of block data across the
> datanodes until deletion is completed. Therefore, the UI should display the
> {*}total replicated pending block size{*}, as this represents the real
> storage consumed in the cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
