[ https://issues.apache.org/jira/browse/HDFS-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172326#comment-13172326 ]
Robert Joseph Evans commented on HDFS-2704: ------------------------------------------- That is a great point. I would suggest that we output a warning/error the first time this happens for each disk and possibly include a metric for it. For all file systems that I know of that have a static number of inodes the ratio of inodes to disk space is configurable and even if it requires reformatting the drive, knowing that it is a problem will allow operations to possibly adjust that ratio appropriately. > 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