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 "Sanghyun Yun (JIRA)" <ji...@apache.org> on 2014/04/29 06:51:20 UTC
[jira] [Commented] (HDFS-5147) Certain dfsadmin commands such as
safemode do not interact with the active namenode in ha setup
[ https://issues.apache.org/jira/browse/HDFS-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983998#comment-13983998 ]
Sanghyun Yun commented on HDFS-5147:
------------------------------------
hdfs dfsadmin -safemode enter
This command's result is first namenode(it doesn't matter that active) status changes to safemode. I think should be changed active namenode or both.
hdfs dfsadmin -fs hdfs://CLUSTERNAME -safemode enter
This command's result is same.
Is it correct?
I performed in r2.2.0
> Certain dfsadmin commands such as safemode do not interact with the active namenode in ha setup
> -----------------------------------------------------------------------------------------------
>
> Key: HDFS-5147
> URL: https://issues.apache.org/jira/browse/HDFS-5147
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.1.0-beta
> Reporter: Arpit Gupta
> Assignee: Jing Zhao
>
> There are certain commands in dfsadmin return the status of the first namenode specified in the configs rather than interacting with the active namenode
> For example. Issue
> hdfs dfsadmin -safemode get
> and it will return the status of the first namenode in the configs rather than the active namenode.
> I think all dfsadmin commands should determine which is the active namenode do the operation on it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)