hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8277) Safemode enter fails when Standby NameNode is down
Date Sat, 09 May 2015 01:56:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536109#comment-14536109
] 

Brahma Reddy Battula commented on HDFS-8277:
--------------------------------------------

I think, we no need to execute the safemode command on standby Node ( anyway it might not
be useful also )..we can get Active Namenode IP and execute is enough..what do you think..?

> 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
>            Assignee: surendra singh lilhore
>            Priority: Minor
>         Attachments: 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
(v6.3.4#6332)

Mime
View raw message