[ https://issues.apache.org/jira/browse/HDFS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426336#comment-13426336 ]
Brahma Reddy Battula commented on HDFS-3744: -------------------------------------------- {quote} The issue is that some dsfadmin commands need to perform client-side failover and talk to the appropriate NN, while others should actually be run against both NNs. {quote} But if we do client-side failover also,I think BNN will not come know. We need to execute command on both NN's. > Decommissioned nodes are included in cluster after switch which is not > expected > ------------------------------------------------------------------------------- > > Key: HDFS-3744 > URL: https://issues.apache.org/jira/browse/HDFS-3744 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha > Affects Versions: 2.0.0-alpha, 2.1.0-alpha, 2.0.1-alpha > Reporter: Brahma Reddy Battula > > Scenario: > ========= > Start ANN and SNN with three DN's > Exclude DN1 from cluster by using decommission feature > (./hdfs dfsadmin -fs hdfs://ANNIP:8020 -refreshNodes) > After decommission successful,do switch such that SNN will become Active. > Here exclude node(DN1) is included in cluster.Able to write files to excluded > node since it's not excluded. > Checked SNN(Which Active before switch) UI decommissioned=1 and ANN UI > decommissioned=0 > One more Observation: > ==================== > All dfsadmin commands will create proxy only on nn1 irrespective of Active or > standby.I think this also we need to re-look once.. > I am not getting , why we are not given HA for dfsadmin commands..? > Please correct me,,If I am wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira