[
https://issues.apache.org/jira/browse/HDFS-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984077#comment-13984077
]
Vinayakumar B commented on HDFS-5147:
-------------------------------------
For getting the safemode status from active namenode we have an option.
see {{DistributedFileSystem#isInSafeMode()}}
{code} public boolean isInSafeMode() throws IOException {
return setSafeMode(SafeModeAction.SAFEMODE_GET, true);
}{code}
here {{isChecked}} is passed as true, then StandByException is thrown from
Standby and request will be processed only at the Active NN.
Same we can have in DFSAdmin call to setSafeMode, may be based on some flag if
required.
Similar changes can be done for other RPCs also which needs to be processed
only at the ActiveNN.
> 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)
