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 "Sailesh Patel (JIRA)" <ji...@apache.org> on 2019/04/23 01:36:00 UTC
[jira] [Created] (HDFS-14448) Provide an appropriate Message when
Secondary Namenode is not bootstrap initialized
Sailesh Patel created HDFS-14448:
------------------------------------
Summary: Provide an appropriate Message when Secondary Namenode is not bootstrap initialized
Key: HDFS-14448
URL: https://issues.apache.org/jira/browse/HDFS-14448
Project: Hadoop HDFS
Issue Type: Improvement
Components: hdfs
Affects Versions: 2.6.0
Reporter: Sailesh Patel
After HDFS is running for some time and then it is enabled for HDFS-HA, if the secondary bootstrap fails ( say because active NN was down), and then it is attempted to be started, the message in secondary NN says "NameNode is not formatted."
e.g.
2019-04-16 19:43:27,951 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: Failed to start namenode. java.io.IOException: NameNode is not formatted. at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:232) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1144)
Can this message be improved to say:
"Secondary NameNode is not initialized. Please Bootstrap Secondary Namenode"
or
"NameNode is not formatted/Secondary Namenode not Bootstrapped(Initialized)"
This is to avoid customers mistakenly formatting namenode and there by losing data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org