You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Danny Becker (Jira)" <ji...@apache.org> on 2023/09/01 03:10:00 UTC
[jira] [Commented] (HDFS-17167) Observer NameNode -observer startup option conflicts with -rollingUpgrade startup option
[ https://issues.apache.org/jira/browse/HDFS-17167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761157#comment-17761157 ]
Danny Becker commented on HDFS-17167:
-------------------------------------
[HDFS-17167. Add config to startup NameNode as Observer by dannytbecker · Pull Request #6013 · apache/hadoop (github.com)|https://github.com/apache/hadoop/pull/6013]
> Observer NameNode -observer startup option conflicts with -rollingUpgrade startup option
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-17167
> URL: https://issues.apache.org/jira/browse/HDFS-17167
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.3.4
> Reporter: Danny Becker
> Priority: Minor
> Attachments: HDFS-17167.001.patch
>
>
> NameNode currently uses a "StartupOption" to decide whether to start a node as an Observer NameNode. This causes an issue during a rolling upgrade because "rollingUpgrade" is also a StartupOption and NameNode will only allow 1 startup option, choosing the last startup option in the list. Observer in our environment starts with the following startup options: ["-rollingUpgrade", "started", "-observer"]. This means that the rolling upgrade gets ignored which causes Observer to have an issue when an actual rolling upgrade is ongoing:
> {code:java}
> 2023-08-23T14:59:03.486-0700,WARN,[main],org.apache.hadoop.hdfs.server.namenode.FSNamesystem,"Encountered exception loading fsimage
> java.io.IOException:
> File system image contains an old layout version -63.
> An upgrade to version -66 is required.
> Please restart NameNode with the \'-rollingUpgrade started\' option if a rolling upgrade is already started; or restart NameNode with the \'-upgrade\' option to start a new upgrade.
> at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:271)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1116)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:724)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:681)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:763)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:1013)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:992)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1743)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1811)
> "{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org