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 "Kaushik Mandal (Jira)" <ji...@apache.org> on 2022/06/21 14:44:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17556945#comment-17556945 ] 

Kaushik Mandal commented on HDFS-4957:
--------------------------------------

I too facing the following scenario:
I have an HA HDFS setup where one of the JN is colocated on the same machine as the active NN.When I shut down the active NN machine, I expect he standby NN to become active. However, the automatic failover fails with : Unable to construct journal exception.

is there any solution or workaround for this issue. Namenode HA is not working using QJM  

> 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 McCabe
>            Assignee: John Zhuge
>            Priority: Major
>
> 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
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org