[ https://issues.apache.org/jira/browse/HDFS-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067473#comment-14067473 ]
Hudson commented on HDFS-6597: ------------------------------ FAILURE: Integrated in Hadoop-Yarn-trunk #617 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/617/]) HDFS-6597. Add a new option to NN upgrade to terminate the process after upgrade on NN is completed. Contributed by Danilo Vunjak. (cnauroth: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1611723) * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/common/HdfsServerConstants.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestStartupOptionUpgrade.java > Add a new option to NN upgrade to terminate the process after upgrade on NN > is completed > ---------------------------------------------------------------------------------------- > > Key: HDFS-6597 > URL: https://issues.apache.org/jira/browse/HDFS-6597 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Affects Versions: 3.0.0, 2.5.0 > Reporter: Danilo Vunjak > Assignee: Danilo Vunjak > Fix For: 3.0.0, 2.6.0 > > Attachments: HDFS-6597.04.patch, HDFS-6597.05.patch, > HDFS-6597.06.patch, JIRA-HDFS-30.patch, JIRA-HDFS-6597.02.patch, > JIRA-HDFS-6597.03.patch, JIRA-HDFS-6597.patch > > > Currently when namenode is started for upgrade (hadoop namenode -upgrade > command), after finishing upgrade of metadata, namenode starts working > normally and wait for datanodes to upgrade itself and connect to to NN. We > need to have option for upgrading only NN metadata, so after upgrade is > finished on NN, process should terminate. > I have tested it by changing in file: hdfs.server.namenode.NameNode.java, > method: public static NameNode createNameNode(String argv[], Configuration > conf): > in switch added > case UPGRADE: > case UPGRADE: > { > DefaultMetricsSystem.initialize("NameNode"); > NameNode nameNode = new NameNode(conf); > if (startOpt.getForceUpgrade()) { > terminate(0); > return null; > } > > return nameNode; > } > This did upgrade of metadata, closed process after finished, and later when > all services were started, upgrade of datanodes finished sucessfully and > system run . > What I'm suggesting right now is to add new startup parameter "-force", so > namenode can be started like this "hadoop namenode -upgrade -force", so we > can indicate that we want to terminate process after upgrade metadata on NN > is finished. Old functionality should be preserved, so users can run "hadoop > namenode -upgrade" on same way and with same behaviour as it was previous. > Thanks, > Danilo -- This message was sent by Atlassian JIRA (v6.2#6252)