You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/07/04 00:48:20 UTC

[jira] [Created] (HDFS-4957) NameNode failover should not fail because a DNS entry for a quorum node cannot be resolved

Colin Patrick McCabe created HDFS-4957:
------------------------------------------

             Summary: 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.2.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira