[
https://issues.apache.org/jira/browse/HDFS-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759739#comment-13759739
]
Jing Zhao commented on HDFS-5147:
---------------------------------
For commands like -safemode and -metasave, currently the NN side's check is
"OperationCategory.UNCHECKED" (since we should allow admin to do it on both
active and standby NN), thus the client will not get a StandbyException if it
goes to the SBN. In that case, it is difficult for the client to make sure it
goes to the "currently active" NN. Even if the client first calls an operation
such as "getFileInfo" before it makes the real call (to trigger its own
failover), NN failover may happen between the interval of two client operations.
So given that we can use -fs option to specify which NN to connect to, I think
maybe we do not need to do anything here.
> 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
