You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2015/02/18 20:48:11 UTC
[jira] [Updated] (HDFS-7810) Datanode registration process fails in
hadoop 2.6
[ https://issues.apache.org/jira/browse/HDFS-7810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Biju Nair updated HDFS-7810:
----------------------------
Description:
When a new DN is added to the cluster, the registration process fails. The following are the steps followed.
- Install and start a new DN
- Add entry for the DN in the NN {{/etc/hosts}} file
DN log shows that the registration process failed
- Tried to restart DN with the same result
Since all the DNs have multiple NW interface, we are using the following {{hdfs-site.xml}} property, instead of listing all the {{dfs.datanode.*.address}} properties.
{code:xml}
<property>
<name>dfs.datanode.dns.interface</name>
<value>eth2</value>
</property>
{code}
- Restarting the NN resolves the issue with registration which is not desired.
- Adding the {{dfs.datanode.*.address}} properties seem to resolve DN registration process without NN restart. But this is a different behavior compared to *hadoop 2.2*. Is there a reason for the change?
was:
When a new DN is added to the cluster, the registration process fails. The following are the steps followed.
- Install and start a new DN
- Add entry for the DN in the {{/etc/hosts}} file
DN log shows that the registration process failed
- Tried to restart DN with the same result
Since all the DNs have multiple NW interface, we are using the following {{hdfs-site.xml}} property, instead of listing all the {{dfs.datanode.*.address}} properties.
{code:xml}
<property>
<name>dfs.datanode.dns.interface</name>
<value>eth2</value>
</property>
{code}
- Restarting the NN resolves the issue with registration which is not desired.
- Adding the {{dfs.datanode.*.address}} properties seem to resolve DN registration process without NN restart. But this is a different behavior compared to *hadoop 2.2*. Is there a reason for the change?
> Datanode registration process fails in hadoop 2.6
> --------------------------------------------------
>
> Key: HDFS-7810
> URL: https://issues.apache.org/jira/browse/HDFS-7810
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode, namenode
> Affects Versions: 2.6.0
> Environment: ubuntu 12
> Reporter: Biju Nair
> Labels: hadoop
>
> When a new DN is added to the cluster, the registration process fails. The following are the steps followed.
> - Install and start a new DN
> - Add entry for the DN in the NN {{/etc/hosts}} file
> DN log shows that the registration process failed
> - Tried to restart DN with the same result
> Since all the DNs have multiple NW interface, we are using the following {{hdfs-site.xml}} property, instead of listing all the {{dfs.datanode.*.address}} properties.
> {code:xml}
> <property>
> <name>dfs.datanode.dns.interface</name>
> <value>eth2</value>
> </property>
> {code}
> - Restarting the NN resolves the issue with registration which is not desired.
> - Adding the {{dfs.datanode.*.address}} properties seem to resolve DN registration process without NN restart. But this is a different behavior compared to *hadoop 2.2*. Is there a reason for the change?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)