[ https://issues.apache.org/jira/browse/HDFS-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737436#comment-13737436 ]
Hadoop QA commented on HDFS-5080: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12597544/HDFS-5080.001.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 1 new or modified test files. {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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.TestNamenodeRetryCache {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/4805//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4805//console This message is automatically generated. > BootstrapStandby not working with QJM when the existing NN is active > -------------------------------------------------------------------- > > Key: HDFS-5080 > URL: https://issues.apache.org/jira/browse/HDFS-5080 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: Jing Zhao > Assignee: Jing Zhao > Attachments: HDFS-5080.000.patch, HDFS-5080.001.patch > > > Currently when QJM is used, running BootstrapStandby while the existing NN is > active can get the following exception: > {code} > FATAL ha.BootstrapStandby: Unable to read transaction ids 6175397-6175405 > from the configured shared edits storage. Please copy these logs into the > shared edits storage or call saveNamespace on the active node. > Error: Gap in transactions. Expected to be able to read up until at least > txid 6175405 but unable to find any edit logs containing txid 6175405 > java.io.IOException: Gap in transactions. Expected to be able to read up > until at least txid 6175405 but unable to find any edit logs containing txid > 6175405 > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.checkForGaps(FSEditLog.java:1300) > at > org.apache.hadoop.hdfs.server.namenode.FSEditLog.selectInputStreams(FSEditLog.java:1258) > at > org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.checkLogsAvailableForRead(BootstrapStandby.java:229) > {code} > Looks like the cause of the exception is that, when the active NN is queries > by BootstrapStandby about the last written transaction ID, the in-progress > edit log segment is included. However, when journal nodes are asked about the > last written transaction ID, in-progress edit log is excluded. This causes > BootstrapStandby#checkLogsAvailableForRead to complain gaps. > To fix this, we can either let journal nodes take into account the > in-progress editlog, or let active NN exclude the in-progress edit log > segment. -- 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