[
https://issues.apache.org/jira/browse/HDFS-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-2820:
------------------------------
Attachment: hdfs-2820.txt
Here's an example output, when I try to start a NN on a machine which is not
one of the NNs specified:
12/01/20 16:27:35 INFO namenode.FSNamesystem: HA Enabled: false
12/01/20 16:27:35 WARN namenode.FSNamesystem: Configured NNs:
Nameservice <ha-nn-uri>:
NN ID nn1 => styx01.sf.cloudera.com/172.29.5.192:8021
NN ID nn2 => styx02.sf.cloudera.com/172.29.5.193:8021
12/01/20 16:27:35 ERROR namenode.FSNamesystem: FSNamesystem initialization
failed.
java.io.IOException: Invalid configuration: a shared edits dir must not be
specified if HA is not enabled.
> Add a simple sanity check for HA config
> ---------------------------------------
>
> Key: HDFS-2820
> URL: https://issues.apache.org/jira/browse/HDFS-2820
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Trivial
> Attachments: hdfs-2820.txt
>
>
> If the user configures a shared edits dir, but doesn't configure the namenode
> addresses correctly, the NN will fail to start up in a very strange way.
> I had this misconfiguration in one of my test clusters which was difficult to
> debug, even though I'm very familiar with the code. This patch is to add a
> simple sanity check so that if a user has the same misconfiguration, it will
> fail to start and given a more informative dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
