[jira] [Commented] (HDFS-5147) Certain dfsadmin commands such as safemode do not interact with the active namenode in ha setup

[Vinayakumar B (JIRA)]

    [ 
https://issues.apache.org/jira/browse/HDFS-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984078#comment-13984078
 ] 

Vinayakumar B commented on HDFS-5147:
-------------------------------------

Adding to above comment, 
in NameNodeRpcServer checks for handled based on the flag passed.
{code}  @Override // ClientProtocol
  public boolean setSafeMode(SafeModeAction action, boolean isChecked)
      throws IOException {
    OperationCategory opCategory = OperationCategory.UNCHECKED;
    if (isChecked) {
      if (action == SafeModeAction.SAFEMODE_GET) {
        opCategory = OperationCategory.READ;
      } else {
        opCategory = OperationCategory.WRITE;
      }
    }
    namesystem.checkOperation(opCategory);
    return namesystem.setSafeMode(action);
  }{code}

> 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)