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/03/24 23:37:27 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=12849504#action_12849504 ]
Suresh Srinivas commented on HDFS-132:
--------------------------------------
{{FSDirectory.directoryMetrics}} reports two metrics - files_created and files_deleted. This is unnecessary as it is already covered by the NameNodeMetrics "FilesCreated" and "DeletedFileOps".
I propose deleting file_created and files_deleted metrics from FSDirectory.directoryMetrics. With that directoryMetrics will be reporting nothing. We could leave it in FSDirectory for future use or delete it altogether.
> 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
> Reporter: Hairong Kuang
>
> 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.