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 "Jianfei Jiang (JIRA)" <ji...@apache.org> on 2018/09/13 06:31:00 UTC
[jira] [Comment Edited] (HDFS-8277) Safemode enter fails when
Standby NameNode is down
[ https://issues.apache.org/jira/browse/HDFS-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580777#comment-16580777 ]
Jianfei Jiang edited comment on HDFS-8277 at 9/13/18 6:30 AM:
--------------------------------------------------------------
Hi
[~brahmareddy], [~arpitagarwal], [~vinayrpet]
As the commands in DFSAdmin except safemode have been fixed in HDFS-12935 before some months. Safemode command has not been fixed for a long time, could we fix it now. I have uploaded HDFS-8277_5.patch like what I did in 12935. Hope to solve this issue asap as it is actually a bug in some cases.
was (Author: jiangjianfei):
Hi
[~brahmareddy]
As the commands in DFSAdmin except safemode have been fixed in HDFS-12935 before some months. Safemode command has not been fixed for a long time, could we fix it now. I have uploaded HDFS-8277_5.patch like what I did in 12935. Hope to solve this issue asap as it is actually a bug in some cases.
> 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: Jianfei Jiang
> 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-8277_5.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org