[
https://issues.apache.org/jira/browse/HDFS-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047735#comment-18047735
]
ASF GitHub Bot commented on HDFS-13775:
---------------------------------------
github-actions[bot] commented on PR #406:
URL: https://github.com/apache/hadoop/pull/406#issuecomment-3693512823
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Add a conf property to retry dns reverse lookups during datanode registration
> -----------------------------------------------------------------------------
>
> Key: HDFS-13775
> URL: https://issues.apache.org/jira/browse/HDFS-13775
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Aniket Namadeo Mokashi
> Priority: Major
>
> During DN registration, if the ip and the hostname in the DN InetAddress are
> the same (i.e. reverse name lookup falied; see [the
> javadoc|http://docs.oracle.com/javase/6/docs/api/java/net/InetAddress.html#getHostName%28%29]),
> the DN will be disallowed to register, where the DN InetAddress was obtained
> from the socket. It is a performance improvement added by HDFS-3990 to avoid
> unnecessary DNS resolutions. However, in an environment where DNS lookups can
> be flaky this can cause datanode registration to fail permanently.
> We propose to add a conf property to retry DNS reverse lookup during DN
> registration. Otherwise, clusters with flaky reverse DNS lookup will fail
> permanently.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
