[
https://issues.apache.org/jira/browse/HDFS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572944#comment-13572944
]
Eli Collins commented on HDFS-4471:
-----------------------------------
If the getConnectAddress method is broken we should fix the other use of it
that was introduced in HDFS-3932 while we're at it, otherwise we have this
correct fix with another incorrect fix so we're broken anyway.
However, NetUtils#getConnectAddress is deterministic, it uses
InetAddress.html#getLocalHost which is based on the host configuration (a lot
of apps would break if that was non-deterministic!). I think
request#getRequestURL works when everyone binds to the wildcard but I think
this breaks when the NN rpc addr is _not_ bound to the wildcard but the http
address is (because it assumes the NN is listening on the same IP the http
request was handled on, which isn't necessarily true).
> Namenode WebUI file browsing does not work with wildcard addresses configured
> -----------------------------------------------------------------------------
>
> Key: HDFS-4471
> URL: https://issues.apache.org/jira/browse/HDFS-4471
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Attachments: hdfs-4471-1.patch, hdfs-4471-2.patch
>
>
> The namenode web UI currently passes around the NN's configured RPC address
> in the URL. One of the places this is used is for file browsing; the NN
> redirects to a random DN, and the DN then uses the NN address from the URL to
> contact the NN. However, this fails when the NN RPC address is configured to
> be the wildcard (0.0.0.0).
> The fix is the same as in HDFS-3932: pass the configured address through
> {{NetUtils#getConnectAddress}} first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
