You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/09/06 19:10:37 UTC

[jira] Resolved: (HADOOP-1704) Throttling for HDFS Trash purging

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

dhruba borthakur resolved HADOOP-1704.
--------------------------------------

    Resolution: Cannot Reproduce

We have not been able to experimentally observe significant increase in memory usage when large number of files are deleted.

> 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.