[
https://issues.apache.org/jira/browse/HDFS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-132:
---------------------------------
Component/s: name-node
Priority: Minor (was: Major)
Affects Version/s: 0.22.0
0.21.0
0.20.3
Fix Version/s: 0.22.0
Release Note:
With this incompatible change, under metrics context "dfs", the record name
"FSDirectory" is no longer available. The metrics "files_deleted" from the
deleted record "FSDirectory" is now available in metrics context "dfs", record
name "namenode" with the metrics name "FilesDeleted".
Hadoop Flags: [Incompatible change, Reviewed]
> 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.22.0
>
> Attachments: HDFS-132.1.patch, HDFS-132.2.patch, HDFS-132.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.
