[
https://issues.apache.org/jira/browse/HADOOP-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525486
]
Doug Cutting commented on HADOOP-1704:
--------------------------------------
> Why not just apply that throttling code to trash as well?
If this is really a problem, that wouldn't fix it when an application deletes a
bunch of files. So, if throttling is required for deletions, we should
implement it generically, either on the namenode or in DFSClient. But, as of
yet, there's no evidence that throttling is required.
> Throttling for HDFS Trash purging
> ---------------------------------
>
> Key: HADOOP-1704
> URL: https://issues.apache.org/jira/browse/HADOOP-1704
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
>
> When HDFS Trash is enabled, deletion of a file/directory results in it being
> moved to the "Trash" directory. The "Trash" directory is periodically purged
> by the Namenode. This means that all files/directories that users deleted in
> the last Trash period, gets "really" deleted when the Trash purging occurs.
> This might cause a burst of file/directory deletions.
> The Namenode tracks blocks that belonged to deleted files in a data structure
> named "RecentInvalidateSets". There is a possibility that Trash purging may
> cause this data structure to bloat, causing undesireable behaviour of the
> Namenode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
