[jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693036#comment-13693036 ] Hudson commented on HDFS-4927: -- Integrated in Hadoop-Mapreduce-trunk #1468 (See [https://buil

[jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693006#comment-13693006 ] Hudson commented on HDFS-4927: -- Integrated in Hadoop-Hdfs-trunk #1441 (See [https://builds.ap

[jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692916#comment-13692916 ] Hudson commented on HDFS-4927: -- Integrated in Hadoop-Yarn-trunk #251 (See [https://builds.apa

[jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692757#comment-13692757 ] Hudson commented on HDFS-4927: -- Integrated in Hadoop-trunk-Commit #4008 (See [https://builds.

[jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692650#comment-13692650 ] Hadoop QA commented on HDFS-4927: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690852#comment-13690852 ] Chris Nauroth commented on HDFS-4927: - Here is the stack trace that I see on namenode s