[ https://issues.apache.org/jira/browse/HDFS-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569238#comment-13569238 ]
Hadoop QA commented on HDFS-4462: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12567641/HDFS-4462.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 2 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.TestStartupOptionUpgrade {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3937//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3937//console This message is automatically generated. > 2NN will fail to checkpoint after an HDFS upgrade from a pre-federation > version of HDFS > --------------------------------------------------------------------------------------- > > Key: HDFS-4462 > URL: https://issues.apache.org/jira/browse/HDFS-4462 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.0.2-alpha > Reporter: Aaron T. Myers > Assignee: Aaron T. Myers > Attachments: HDFS-4462.patch, HDFS-4462.patch, HDFS-4462.patch > > > The 2NN currently has logic to detect when its on-disk FS metadata needs an > upgrade with respect to the NN's metadata (i.e. the layout versions are > different) and in this case it will proceed with the checkpoint despite > storage signatures not matching precisely if the BP ID and Cluster ID do > match exactly. However, in situations where we're upgrading from versions of > HDFS prior to federation, which had no BP IDs or Cluster IDs, checkpoints > will always fail with an error like the following: > {noformat} > 13/01/31 17:02:25 ERROR namenode.SecondaryNameNode: checkpoint: Inconsistent > checkpoint fields. > LV = -40 namespaceID = 403832480 cTime = 1359680537192 ; clusterId = > CID-0df6ff22-1165-4c7d-9630-429972a7737c ; blockpoolId = > BP-1520616013-172.21.3.106-1359680537136. > Expecting respectively: -19; 403832480; 0; ; . > {noformat} -- 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