[ https://issues.apache.org/jira/browse/HDFS-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron T. Myers updated HDFS-1378: --------------------------------- Attachment: hdfs-1378.1.patch Updated patch which fixes the {{TestEditLog}} test failure. The only difference between my original patch and this one are these lines in {{TestEditLog.java}}: {noformat} - } catch (ChecksumException e) { + } catch (IOException e) { // expected + assertEquals("Cause of exception should be ChecksumException", + e.getCause().getClass(), ChecksumException.class); {noformat} I believe the other test failures are presently failing on trunk. > Edit log replay should track and report file offsets in case of errors > ---------------------------------------------------------------------- > > Key: HDFS-1378 > URL: https://issues.apache.org/jira/browse/HDFS-1378 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Affects Versions: 0.22.0 > Reporter: Todd Lipcon > Assignee: Aaron T. Myers > Fix For: 0.23.0 > > Attachments: hdfs-1378-branch20.txt, hdfs-1378.0.patch, > hdfs-1378.1.patch > > > Occasionally there are bugs or operational mistakes that result in corrupt > edit logs which I end up having to repair by hand. In these cases it would be > very handy to have the error message also print out the file offsets of the > last several edit log opcodes so it's easier to find the right place to edit > in the OP_INVALID marker. We could also use this facility to provide a rough > estimate of how far along edit log replay the NN is during startup (handy > when a 2NN has died and replay takes a while) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira