[ https://issues.apache.org/jira/browse/HDFS-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295210#comment-13295210 ]
Aaron T. Myers commented on HDFS-3521: -------------------------------------- Hey Nicholas, I'm still not entirely convinced of the motivation for this change, and I agree with Colin that we should be careful with respect to what impact this change will have on recovery mode. Given that, I do think we should revert this commit until everyone's satisfied with the changes it makes. I'm sure we can figure out a mutually-agreeable way to address the concerns you have, but let's talk it out for a bit first? > Allow namenode to tolerate edit log corruption > ---------------------------------------------- > > Key: HDFS-3521 > URL: https://issues.apache.org/jira/browse/HDFS-3521 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Reporter: Tsz Wo (Nicholas), SZE > Assignee: Tsz Wo (Nicholas), SZE > Fix For: 1.2.0 > > Attachments: h3521_20120610_b-1.patch, h3521_20120611_b-1.0.patch, > h3521_20120611_b-1.patch > > > HDFS-3479 adds checking for edit log corruption. It uses a fixed > UNCHECKED_REGION_LENGTH (=PREALLOCATION_LENGTH) so that the bytes at the end > within the length is not checked. Instead of not checking the bytes, we > should check everything and allow toleration. -- 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