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 "Eric Walk (JIRA)" <ji...@apache.org> on 2015/08/31 19:44:46 UTC
[jira] [Updated] (HDFS-4957) NameNode failover should not fail
because a DNS entry for a quorum node cannot be resolved
[ https://issues.apache.org/jira/browse/HDFS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Walk updated HDFS-4957:
----------------------------
Affects Version/s: 2.6.0
> NameNode failover should not fail because a DNS entry for a quorum node cannot be resolved
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-4957
> URL: https://issues.apache.org/jira/browse/HDFS-4957
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: qjm
> Affects Versions: 2.3.0, 2.6.0
> Reporter: Colin Patrick McCabe
>
> When a StandbyNameNode is becoming active, we should not bail out because a DNS entry for a quorum node cannot be resolved. Currently it does fail in this scenario, with a message like this:
> {code}
> 2013-07-03 21:28:40,576 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services required for active state
> 2013-07-03 21:28:40,579 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Error encountered requiring NN shutdown. Shutting down immediately.
> java.lang.IllegalArgumentException: Unable to construct journal, qjournal://hadoop-mm:8485;hadoop-nn-0:8485;hadoop-nn-1:8485/hadoop
> at org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1254)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournals(FSEditLog.java:226)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournalsForWrite(FSEditLog.java:193)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startActiveServices(FSNamesystem.java:722)
> <etc>
> {code}
> reported by Matt Bookman
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)