hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1704) Throttling for HDFS Trash purging
Date Sat, 18 Aug 2007 15:20:30 GMT

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

Raghu Angadi commented on HADOOP-1704:

In a recent test of block crc upgrade, Namenode deleted 5M .crc files in SafeMode without
apparent increase in memory. The datanodes were asked to delete the blocks right after SafeMode
was off. Each datanode was asked to delete 16k blocks in total. Even during this time there
was no noticeable increase in memory (may be less than 5-10%).

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

View raw message