Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Tue, 28 Apr 2015 15:09:06 +0000 (UTC)
From: "Hari Sekhon (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12825556.1430233745000.7888.1430233746058@Atlassian.JIRA>
In-Reply-To: <JIRA.12825556.1430233745000@Atlassian.JIRA>
References: <JIRA.12825556.1430233745000@Atlassian.JIRA>
 <JIRA.12825556.1430233745023@arcas>
Subject: [jira] [Created] (HDFS-8277) Safemode enter fails when Standby
 NameNode is down
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hari Sekhon created HDFS-8277:
---------------------------------

             Summary: 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, HDFS, namenode
    Affects Versions: 2.6.0
         Environment: HDP 2.2.0
            Reporter: Hari Sekhon


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.

Hari Sekhon
http://www.linkedin.com/in/harisekhon


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)