hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6073) NameNodeResourceChecker prints 'null' mount point to the log
Date Fri, 04 Apr 2014 05:43:15 GMT

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

Uma Maheswara Rao G commented on HDFS-6073:

Thanks a lot, Akira for patch!
Patch almost looks good except the concern that, your test is on NamenodeResourceChecker,
But bug exist in DF.   We could have written test directly on DF itself, no?
That will also make the code changes only in common now. So we could move this JIRA to common
and update the JIRA title and description?

> NameNodeResourceChecker prints 'null' mount point to the log
> ------------------------------------------------------------
>                 Key: HDFS-6073
>                 URL: https://issues.apache.org/jira/browse/HDFS-6073
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.3.0
>            Reporter: Akira AJISAKA
>            Assignee: Akira AJISAKA
>         Attachments: HDFS-6073.2.patch, HDFS-6073.patch
> If the available space on the volume used for saving fsimage is less than 100MB (default),
NameNodeResourceChecker prints the log as follows:
> {code}
> Space available on volume 'null' is 92274688, which is below the configured reserved
amount 104857600
> {code}
> It should print an appropriate mount point instead of null.

This message was sent by Atlassian JIRA

View raw message