HDDS-16363. Fix split-schema MPU size tracking in Recon event handlers - #11181
Open
priyeshkaratha wants to merge 1 commit into
Open
HDDS-16363. Fix split-schema MPU size tracking in Recon event handlers#11181priyeshkaratha wants to merge 1 commit into
priyeshkaratha wants to merge 1 commit into
Conversation
priyeshkaratha
force-pushed
the
HDDS-16363
branch
2 times, most recently
from
September 1, 2026 08:43
6553694 to
ddc342f
Compare
priyeshkaratha
force-pushed
the
HDDS-16363
branch
from
September 1, 2026 10:26
ddc342f to
836bdf0
Compare
priyeshkaratha
marked this pull request as ready for review
September 2, 2026 05:41
priyeshkaratha
requested review from
ArafatKhan2198,
devmadhuu,
spacemonkd and
sumitagrawl
September 2, 2026 05:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Problem:
The Recon API endpoint /api/v1/keys/open/mpu/summary was returning zero sizes for split-schema multipart uploads (MPUs) because event handlers were not tracking part sizes from the multipartPartsTable. Only legacy-schema MPU sizes
(embedded in multipartInfoTable values) were tracked by events. Split-schema MPU sizes were only calculated during periodic reprocess, causing newly created split-schema MPUs to show zero sizes until the next reprocess run.
Root Cause:
When split-schema MPU support was added (HDDS-14666), the MultipartInfoInsightHandler event methods were updated to use forEachLegacyPart(), which returned early for split-schema MPUs without processing any sizes. Event handlers had no mechanism to access multipartPartsTable to fetch split-schema part sizes incrementally.
Solution:
Extended OmTableHandler interface to pass OMMetadataManager to event handlers, enabling access to multipartPartsTable during event processing.
Added new applySplitSchemaPartSizes() method to MultipartInfoInsightHandler that:
Integrated split-schema size tracking into PUT, DELETE, and UPDATE event handlers.
Updated DeletedKeysInsightHandler and OpenKeysInsightHandler to accept the new OMMetadataManager parameter (no-op for these handlers).
What is the link to the Apache JIRA
HDDS-16363
How was this patch tested?
Tested manually
