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 "Steve Vaughan (Jira)" <ji...@apache.org> on 2022/08/23 19:36:00 UTC
[jira] [Updated] (HDFS-16685) DataNode registration fails because getHostName returns an IP address
[ https://issues.apache.org/jira/browse/HDFS-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Vaughan updated HDFS-16685:
---------------------------------
Affects Version/s: 3.4.0
3.3.9
> DataNode registration fails because getHostName returns an IP address
> ---------------------------------------------------------------------
>
> Key: HDFS-16685
> URL: https://issues.apache.org/jira/browse/HDFS-16685
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.4.0, 3.3.9
> Environment: Run in Kubernetes using Java 11.
> Reporter: Steve Vaughan
> Assignee: Steve Vaughan
> Priority: Major
>
> The call to dnAddress.getHostName() can return an IP address encoded as a string, which is then rejected because unresolved addresses can result in performance impacts due to repetitive DNS lookups later. We can detect when this situation occurs, and perform a DNS reverse name lookup to fix the issue.
> Bouncing a DataNode in a managed environment results in a new IP address allocation, and the new instance fails to register with the NameNode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org