You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2014/05/21 18:00:40 UTC
[jira] [Updated] (AMBARI-5840) Ambari recomission of datanodes will
not work if the active namenode is "nn2"
[ https://issues.apache.org/jira/browse/AMBARI-5840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-5840:
------------------------------------
Description:
PROBLEM: Ambari recomission of datanodes will not work if the active namenode is "nn2"
BUSINESS IMPACT: This will cause a node to not ever be recomissioned if the nn2 machine is the active namenode. Basically, any change that requires a refreshnodes command, will not be applied if nn2 is the active namenode.
STEPS TO REPRODUCE:
1. Create a new cluster with HA for namenode
2. Decomission a datanode
3. Failover the namenode, so the node that corresponds to nn2 is the active namenode.
for example in hdfs-site.xml:
<property>
<name>dfs.namenode.rpc-address.cluster01.nn2</name>
<value>master02.server.com:8020</value>
</property>
the active namenode host would be master02.server.com.
3. Now try to recomission the node.
4. when the process is done as per ambari, execute a hdfs dfsadmin -report and grep for "Decommissioned". You should see that machine you just try to recommission as decomissioned.
ACTUAL BEHAVIOR: The recomission process does not work in ambari if nn2 is the active namenode.
EXPECTED BEHAVIOR: The recomission process should work.
WORKAROUND: Use the command:
hdfs dfsadmin -fs hdfs://<namenodehostactive>:8020 -refreshNodes
This will refreshnodes properly for the active namenode.
was:
PROBLEM: Ambari recomission of datanodes will not work if the active namenode is "nn2"
BUSINESS IMPACT: This will cause a node to not ever be recomissioned if the nn2 machine is the active namenode. Basically, any change that requires a refreshnodes command, will not be applied if nn2 is the active namenode.
STEPS TO REPRODUCE:
1. Create a new cluster with HA for namenode
2. Decomission a datanode
3. Failover the namenode, so the node that corresponds to nn2 is the active namenode.
for example in hdfs-site.xml:
<property>
<name>dfs.namenode.rpc-address.cluster01.nn2</name>
<value>master02.manage.com:8020</value>
</property>
the active namenode host would be master02.manage.com.
3. Now try to recomission the node.
4. when the process is done as per ambari, execute a hdfs dfsadmin -report and grep for "Decommissioned". You should see that machine you just try to recommission as decomissioned.
ACTUAL BEHAVIOR: The recomission process does not work in ambari if nn2 is the active namenode.
EXPECTED BEHAVIOR: The recomission process should work.
WORKAROUND: Use the command:
hdfs dfsadmin -fs hdfs://<namenodehostactive>:8020 -refreshNodes
This will refreshnodes properly for the active namenode.
> Ambari recomission of datanodes will not work if the active namenode is "nn2"
> ------------------------------------------------------------------------------
>
> Key: AMBARI-5840
> URL: https://issues.apache.org/jira/browse/AMBARI-5840
> Project: Ambari
> Issue Type: Bug
> Components: agent
> Affects Versions: 1.5.1
> Environment: java 1.6 update 31
> Centos 6.4
> Not specific to Ambari, but ambari 1.5.1 this was reproduced.
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 1.6.1
>
>
> PROBLEM: Ambari recomission of datanodes will not work if the active namenode is "nn2"
> BUSINESS IMPACT: This will cause a node to not ever be recomissioned if the nn2 machine is the active namenode. Basically, any change that requires a refreshnodes command, will not be applied if nn2 is the active namenode.
> STEPS TO REPRODUCE:
> 1. Create a new cluster with HA for namenode
> 2. Decomission a datanode
> 3. Failover the namenode, so the node that corresponds to nn2 is the active namenode.
> for example in hdfs-site.xml:
> <property>
> <name>dfs.namenode.rpc-address.cluster01.nn2</name>
> <value>master02.server.com:8020</value>
> </property>
> the active namenode host would be master02.server.com.
> 3. Now try to recomission the node.
> 4. when the process is done as per ambari, execute a hdfs dfsadmin -report and grep for "Decommissioned". You should see that machine you just try to recommission as decomissioned.
> ACTUAL BEHAVIOR: The recomission process does not work in ambari if nn2 is the active namenode.
> EXPECTED BEHAVIOR: The recomission process should work.
> WORKAROUND: Use the command:
> hdfs dfsadmin -fs hdfs://<namenodehostactive>:8020 -refreshNodes
> This will refreshnodes properly for the active namenode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)