[
https://issues.apache.org/jira/browse/HDFS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573835#comment-13573835
]
Aaron T. Myers commented on HDFS-4471:
--------------------------------------
Hey Daryn, I think you make a good point. I think the best fix would probably
be to not pass an address at all from the NN to the DN, but instead just pass
the NN's nameservice ID and have the DN look up in its own configs what
address(es) to connect to. This would be a somewhat more involved change,
though.
How about this - given that the proper fix is more involved, and fixing this
issue this way will fix the web UI for many (most?) users, how about we commit
this as-is and file a follow-up JIRA to fix this properly at a later date. Does
this sound OK by you?
> 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
