[jira] [Commented] (HDFS-2704) NameNodeResouceChecker#checkAvailableResources should check for inodes
[ https://issues.apache.org/jira/browse/HDFS-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253149#comment-13253149 ] SreeHari commented on HDFS-2704: Is a low number of fs inodes a problem for namenode ? Since namenode doesn't create new files in the local filesystem (unlike datanode) while it is running , will it be fine if we put nn into safe mode when system run out of inodes ? Or are we talking about just logging a warning ? > 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
[jira] [Commented] (HDFS-2704) NameNodeResouceChecker#checkAvailableResources should check for inodes
[ https://issues.apache.org/jira/browse/HDFS-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172046#comment-13172046 ] SreeHari commented on HDFS-2704: Will give a patch for this . > 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 > > 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
[jira] [Commented] (HDFS-2698) BackupNode is downloading image from NameNode for every checkpoint
[ https://issues.apache.org/jira/browse/HDFS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171873#comment-13171873 ] SreeHari commented on HDFS-2698: Isnt this same as [https://issues.apache.org/jira/browse/HDFS-2007] ? > BackupNode is downloading image from NameNode for every checkpoint > -- > > Key: HDFS-2698 > URL: https://issues.apache.org/jira/browse/HDFS-2698 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node >Affects Versions: 0.22.0 >Reporter: Konstantin Shvachko >Assignee: Konstantin Shvachko > Attachments: rollFSImage.patch, rollFSImage.patch > > > BackupNode can make periodic checkpoints without downloading image and edits > files from the NameNode, but with just saving the namespace to local disks. > This is not happening because NN renews checkpoint time after every > checkpoint, thus making its image ahead of the BN's even though they are in > sync. -- 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
