[ 
https://issues.apache.org/jira/browse/HDFS-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924259#comment-13924259
 ] 

Hudson commented on HDFS-5986:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #5283 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5283/])
HDFS-5986. Capture the number of blocks pending deletion on namenode webUI. 
Contributed by Chris Nauroth. (cnauroth: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1575384)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/metrics/FSNamesystemMBean.java
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/hdfs/dfshealth.html
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSNamesystemMBean.java


> Capture the number of blocks pending deletion on namenode webUI
> ---------------------------------------------------------------
>
>                 Key: HDFS-5986
>                 URL: https://issues.apache.org/jira/browse/HDFS-5986
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Suresh Srinivas
>            Assignee: Chris Nauroth
>         Attachments: HDFS-5986-screenshot.png, HDFS-5986.1.patch
>
>
> When a directory that has large number of directories and files are deleted, 
> the namespace deletes the corresponding inodes immediately. However it is 
> hard to to know when the invalidated blocks are actually deleted on the 
> datanodes, which could take a while.
> I propose adding on namenode webUI, along with under replicated blocks, the 
> number of blocks that are pending deletion.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to