[
https://issues.apache.org/jira/browse/HDDS-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956572#comment-17956572
]
Devesh Kumar Singh commented on HDDS-13186:
-------------------------------------------
[~priyeshkaratha] I think all keys including commited key sizes are already
being computed as part of NSSummary tree and can be accessible using /du API,
so not sure what you want to do extra here ? Can you pls elaborate ?
> Enhance NSSummary to Track Committed Key Size from KeyTable and FileTable
> -------------------------------------------------------------------------
>
> Key: HDDS-13186
> URL: https://issues.apache.org/jira/browse/HDDS-13186
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Priyesh K
> Priority: Major
>
> Description:
> Recon’s NSSummary currently tracks metadata related to open keys and
> directory structures using OM DB events. This JIRA proposes to extend the
> NSSummary framework and metrics pipeline to also track committed key sizes by
> processing entries from the KeyTable and FileTable (both OBS and FSO).
> What needs to be done:
> Update the NSSummary logic to extract size information from committed keys
> during:
> Initial OM DB snapshot load.
> Incremental OM DB updates (PUT/DELETE events for committed keys).
> Track and aggregate committed key sizes per volume/bucket/path.
> Ensure this data is exposed via existing or new Recon metrics.
> (Optional) Integrate with upcoming Cluster Utilization Page for committed
> usage breakdown.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
