[ 
https://issues.apache.org/jira/browse/HDFS-15313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shashikant Banerjee updated HDFS-15313:
---------------------------------------
    Description: After HDFS-13101, it was observed that delete snapshot end up 
cleaning up inodes from active fs which can be referred from only one snapshot 
as the isLastReference() check for the parent dir introduced in HDFS-13101 
returns true. The aim of this Jira to add a check to ensure if the Inodes are 
being referred in the active fs , should not get deleted while deletion of 
snapshot happens.  (was: After HDFS-13101, it was observed that delete snapshot 
end up cleaning up inodes from active fs which can be referred from only one 
snapshot as the isLastReference() introduced in HDFS-13101 returns true. The 
aim of this Jira to add a check to ensure if the Inodes are being referred in 
the active fs , should not get deleted while deletion of snapshot happens.)

> Ensure inodes in active filesytem are not deleted during snapshot delete
> ------------------------------------------------------------------------
>
>                 Key: HDFS-15313
>                 URL: https://issues.apache.org/jira/browse/HDFS-15313
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: snapshots
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 3.4.0
>
>
> After HDFS-13101, it was observed that delete snapshot end up cleaning up 
> inodes from active fs which can be referred from only one snapshot as the 
> isLastReference() check for the parent dir introduced in HDFS-13101 returns 
> true. The aim of this Jira to add a check to ensure if the Inodes are being 
> referred in the active fs , should not get deleted while deletion of snapshot 
> happens.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to