hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-132) Namenode in Safemode reports to Simon non-zero number of deleted files during startup
Date Fri, 02 Apr 2010 21:11:27 GMT

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

Suresh Srinivas updated HDFS-132:
---------------------------------

    Attachment: HDFS-132.1.patch

New version of the patch with minor changes:
# unprotectedDeleted returns the number of deleted inodes and no longer takes logReplay argument.
# unprotectedRenameTo returns boolean to indicate the existing rename target was overwritten.
logReplay argument to the method is removed.

> 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
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-132.1.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.


Mime
View raw message