[
https://issues.apache.org/jira/browse/HDFS-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715116#comment-17715116
]
ASF GitHub Bot commented on HDFS-16972:
---------------------------------------
umamaheswararao commented on PR #5532:
URL: https://github.com/apache/hadoop/pull/5532#issuecomment-1518177291
We had offline discussion on the above comments. The CURRENT_STATE_ID was
coming because it tries to check until CURRENT_STATE_ID.
This fix is basically keeping the given snapshot details in ReclaimContext.
Later before cleaning up, it is making sure that, if the ReclaimContext to be
deleted snapshot is current id, that is basically regular delete file. In
snapshot case, reclaimContext stored snapshot can't be current_state_id, so it
will not clean up.
> Delete a snapshot may deleteCurrentFile
> ---------------------------------------
>
> Key: HDFS-16972
> URL: https://issues.apache.org/jira/browse/HDFS-16972
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
>
> We found one case the when deleting a snapshot (with ordered snapshot
> deletion disabled), it can incorrectly delete some files in the current state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
