[ https://issues.apache.org/jira/browse/HDFS-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601953#comment-13601953 ]
Hadoop QA commented on HDFS-3277: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12573630/HDFS-3277.006.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 6 new or modified test files. {color:green}+1 tests included appear to have a timeout.{color} {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4096//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4096//console This message is automatically generated. > fail over to loading a different FSImage if the first one we try to load is > corrupt > ----------------------------------------------------------------------------------- > > Key: HDFS-3277 > URL: https://issues.apache.org/jira/browse/HDFS-3277 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: Colin Patrick McCabe > Assignee: Andrew Wang > Attachments: HDFS-3277.002.patch, HDFS-3277.003.patch, > HDFS-3277.004.patch, HDFS-3277.005.patch, HDFS-3277.006.patch > > > Most users store multiple copies of the FSImage in order to prevent > catastrophic data loss if a hard disk fails. However, our image loading code > is currently not set up to start reading another FSImage if loading the first > one does not succeed. We should add this capability. > We should also be sure to remove the FSImage directory that failed from the > list of FSImage directories to write to, in the way we normally do when a > write (as opopsed to read) fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira