[
https://issues.apache.org/jira/browse/HDDS-15760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-15760:
------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Handle large or invalid OM snapshot local data YAMLs
> ----------------------------------------------------
>
> Key: HDDS-15760
> URL: https://issues.apache.org/jira/browse/HDDS-15760
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Yashaswini G A
> Assignee: Siyao Meng
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> OM snapshot local data YAML stores SST metadata used by snapshot defrag and
> snapshot diff. For snapshots with many small SST files, this YAML can grow
> beyond SnakeYAML's default 3 MiB code-point limit. When that happens, loading
> the YAML can fail during OM startup or snapshotLocalData initialization.
> Goal: A bad local YAML should not make OM startup fail.
> The YAML is local optimization metadata for snapshot SST/version tracking,
> not the authoritative OM namespace state. If one snapshot's local metadata is
> unreadable or inconsistent, OM should continue loading valid snapshot
> metadata and leave the affected snapshot's defrag/diff path unavailable until
> the YAML is fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
