You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2012/07/31 07:36:35 UTC
[jira] [Created] (HADOOP-8636) Decommissioned nodes are included in
cluster after switch which is not expected
Brahma Reddy Battula created HADOOP-8636:
--------------------------------------------
Summary: Decommissioned nodes are included in cluster after switch which is not expected
Key: HADOOP-8636
URL: https://issues.apache.org/jira/browse/HADOOP-8636
Project: Hadoop Common
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