[
https://issues.apache.org/jira/browse/HDDS-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-15428:
------------------------------
Description:
Problem: OM orphan snapshot cleanup (which removes YAML) could start from an
older queued snapshot before a newer descendant. In linear snapshot chains,
that caused unnecessary early ancestor checks. The newest descendant could
still make cleanup complete in the same drain, but older snapshots were
revisited later in that drain after they became eligible.
Goal: Remove purged snapshot YAMLs (that are eligible to be removed, inDegree
== 0) in one run
was:
Problem: OM orphan snapshot cleanup (which removes YAML) could start from an
older queued snapshot before a newer descendant. In linear snapshot chains,
that caused unnecessary early ancestor checks. The newest descendant could
still make cleanup complete in the same drain, but older snapshots were
revisited later in that drain after they became eligible.
Goal: Remove purged snapshot YAMLs (that are eligible to be removed) in one run
> Remove purged snapshot YAMLs in one run
> ---------------------------------------
>
> Key: HDDS-15428
> URL: https://issues.apache.org/jira/browse/HDDS-15428
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Snapshot
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
>
> Problem: OM orphan snapshot cleanup (which removes YAML) could start from an
> older queued snapshot before a newer descendant. In linear snapshot chains,
> that caused unnecessary early ancestor checks. The newest descendant could
> still make cleanup complete in the same drain, but older snapshots were
> revisited later in that drain after they became eligible.
> Goal: Remove purged snapshot YAMLs (that are eligible to be removed, inDegree
> == 0) in one run
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
