[
https://issues.apache.org/jira/browse/HDDS-14654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-14654:
----------------------------------
Labels: pull-request-available (was: )
> NoSuchFileException when orphan check runs after purged snapshot YAML is
> deleted
> --------------------------------------------------------------------------------
>
> Key: HDDS-14654
> URL: https://issues.apache.org/jira/browse/HDDS-14654
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Sadanand Shenoy
> Assignee: Sadanand Shenoy
> Priority: Major
> Labels: pull-request-available
>
> When a purged snapshot’s YAML is deleted (all versions removed), the orphan
> check can still schedule that snapshot again.
> The next run then tries to load the missing YAML and throws
> NoSuchFileException.
> Root cause
> In checkForOphanVersionsAndIncrementCount, we always call
> incrementOrphanCheckCount(snapshotId) when isPurgeTransactionSet or the
> version changes, even if the YAML was just deleted (empty versions). That
> keeps the snapshot in snapshotToBeCheckedForOrphans even though there is
> nothing left to check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
