[
https://issues.apache.org/jira/browse/HDFS-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756184#comment-13756184
]
Konstantin Shvachko commented on HDFS-5147:
-------------------------------------------
> Also we should add an optional argument to take in the namenode hostname or
> dfs.ha.namenodes.
This is already available with -fs generic option.
> value so the user can do admin operation on any namenode.
Very good idea. If I understand it correctly:
- If -fs is specified the command is sent to that particular NameNode.
- And by default to the active NN.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
