[jira] [Resolved] (HDFS-82) recentInvalidateSets in FSNamesystem is not required

["Harsh J (Resolved) (JIRA)" <ji...@apache.org>]

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

Harsh J resolved HDFS-82.
-------------------------

    Resolution: Not A Problem

This has been resolved on trunk. We only have one set.
                
> recentInvalidateSets in FSNamesystem is not required 
> -----------------------------------------------------
>
>                 Key: HDFS-82
>                 URL: https://issues.apache.org/jira/browse/HDFS-82
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Raghu Angadi
>
> See HADOOP-2576 for more background. 
> When a file is deleted, blocks are first placed in recentInvalidateSets and then later computeDatanodeWork moves it to 'invalidateSet' for each datanode. 
> I could not see why a block is placed in this intermediate set. I think it is confusing as well.. for example, -metasave prints blocks from only one list. Unless we read very carefully its not easy to figure out that there are two lists. My proposal is to keep only one of them.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira