hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2704) NameNodeResouceChecker#checkAvailableResources should check for inodes
Date Fri, 13 Apr 2012 20:59:18 GMT

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

Aaron T. Myers commented on HDFS-2704:

bq. having a corrupted edit log because we tried to roll them when there were no inodes available
is a very bad thing.

Certainly true, though it seems unlikely that this would result in a truly corrupt edit log
that the NN couldn't restart from, since running out of inodes would presumably result in
no file being created at all, which isn't an invalid edit log.

bq. NameNode also does create local image/edits files upon every checkpointing and such -
so the inode monitoring is surely relevant.

> NameNodeResouceChecker#checkAvailableResources should check for inodes
> ----------------------------------------------------------------------
>                 Key: HDFS-2704
>                 URL: https://issues.apache.org/jira/browse/HDFS-2704
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.24.0
>            Reporter: Eli Collins
>            Assignee: SreeHari
> NameNodeResouceChecker#checkAvailableResources currently just checks for free space.
However inodes are also a file system resource that needs to be available (you can run out
of inodes but have free space).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message