[
https://issues.apache.org/jira/browse/HDFS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572810#comment-13572810
]
Daryn Sharp commented on HDFS-4471:
-----------------------------------
{{NetUtils.getConnectAddress}} is going to just return the first interface on
the machine, which is non-deterministic. It might be the loopback, a vpn
tunnel, an ethernet interface, etc. What you really want to do is return
exactly the same authority the client used to contact the server. This is
completely untested, but probably will do the trick:
{code}
String addr = URI.create(request.getRequestURL().toString()).getAuthority();
{code}
> 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
>
>
> 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
