You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2010/07/13 02:19:50 UTC
[jira] Commented: (HDFS-132) Namenode in Safemode reports to Simon
non-zero number of deleted files during startup
[ https://issues.apache.org/jira/browse/HDFS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887598#action_12887598 ]
Suresh Srinivas commented on HDFS-132:
--------------------------------------
+1 for the 20 and y20 version of the patch.
> Namenode in Safemode reports to Simon non-zero number of deleted files during startup
> -------------------------------------------------------------------------------------
>
> Key: HDFS-132
> URL: https://issues.apache.org/jira/browse/HDFS-132
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.20.3, 0.21.0, 0.22.0
> Reporter: Hairong Kuang
> Assignee: Suresh Srinivas
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HDFS-132-20.patch, HDFS-132.1.patch, HDFS-132.2.patch, HDFS-132.patch, HDFS-132.y20.patch
>
>
> Currently when a namenode starts up it may call "delete" when loading edits. But metrics file_deleted is collected and reported in FSDirectory where it does not and is not able to check if namenode is in safemode. So from the monitoring UI, we see non-zero number of files deleted.
> A possible fix is to have delete to return the number of files deleted and then the metrics is collected and reported at NameNode the same as other namenode metrics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.