[ https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365168#comment-16365168 ]
Surendra Singh Lilhore commented on HDFS-8277: ---------------------------------------------- Hi, [~arpitagarwal], [~vinayrpet] and [~brahmareddy] We got the same issue in production environment. Can we finalized the solution for this Jira ?. > Safemode enter fails when Standby NameNode is down > -------------------------------------------------- > > Key: HDFS-8277 > URL: https://issues.apache.org/jira/browse/HDFS-8277 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, namenode > Affects Versions: 2.6.0 > Environment: HDP 2.2.0 > Reporter: Hari Sekhon > Assignee: Surendra Singh Lilhore > Priority: Major > Attachments: HDFS-8277-safemode-edits.patch, HDFS-8277.patch, > HDFS-8277_1.patch, HDFS-8277_2.patch, HDFS-8277_3.patch, HDFS-8277_4.patch > > > HDFS fails to enter safemode when the Standby NameNode is down (eg. due to > AMBARI-10536). > {code}hdfs dfsadmin -safemode enter > safemode: Call From nn2/x.x.x.x to nn1:8020 failed on connection exception: > java.net.ConnectException: Connection refused; For more details see: > http://wiki.apache.org/hadoop/ConnectionRefused{code} > This appears to be a bug in that it's not trying both NameNodes like the > standard hdfs client code does, and is instead stopping after getting a > connection refused from nn1 which is down. I verified normal hadoop fs writes > and reads via cli did work at this time, using nn2. I happened to run this > command as the hdfs user on nn2 which was the surviving Active NameNode. > After I re-bootstrapped the Standby NN to fix it the command worked as > expected again. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org