You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2020/07/18 19:11:00 UTC
[jira] [Updated] (HDFS-15477) Enforce in-order snapshot deletion
[ https://issues.apache.org/jira/browse/HDFS-15477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze updated HDFS-15477:
------------------------------
Description:
Snapshot deletion has caused a few bugs earlier such as HDFS-13101 and HDFS-15313. In this JIRA, we propose enforcing in-order snapshot deletion -- only the earliest snapshot is actually deleted from the file system. The other snapshots are only marked as deleted. They will be actually deleted from the file system until all the earlier snapshots are deleted.
The reason of enforcing in-order snapshot deletion is based on the observation that the logic of deleting the earliest snapshot is much simpler since the prior snapshot does not exist. All the previous bugs are caused by removing inodes from the prior snapshots.
One drawback of in-order snapshot deletion is that the non-earliest snapshots are only marked as deleted but not actually deleted. The resources are not yet released.
was:
Snapshot deletion has caused a few bugs earlier such as HDFS-13101 and HDFS-15313. In this JIRA, we propose enforcing in-order snapshot deletion -- only the earliest snapshot is actually deleted from the file system. The other snapshots are only marked as deleted. They will be actually deleted from the file system until all the earlier snapshots are deleted.
> Enforce in-order snapshot deletion
> ----------------------------------
>
> Key: HDFS-15477
> URL: https://issues.apache.org/jira/browse/HDFS-15477
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
>
> Snapshot deletion has caused a few bugs earlier such as HDFS-13101 and HDFS-15313. In this JIRA, we propose enforcing in-order snapshot deletion -- only the earliest snapshot is actually deleted from the file system. The other snapshots are only marked as deleted. They will be actually deleted from the file system until all the earlier snapshots are deleted.
> The reason of enforcing in-order snapshot deletion is based on the observation that the logic of deleting the earliest snapshot is much simpler since the prior snapshot does not exist. All the previous bugs are caused by removing inodes from the prior snapshots.
> One drawback of in-order snapshot deletion is that the non-earliest snapshots are only marked as deleted but not actually deleted. The resources are not yet released.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org