[
https://issues.apache.org/jira/browse/HDFS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574107#comment-13574107
]
Hudson commented on HDFS-4471:
------------------------------
Integrated in Hadoop-trunk-Commit #3344 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3344/])
HDFS-4471. Namenode WebUI file browsing does not work with wildcard
addresses configured. Contributed by Andrew Wang. (Revision 1443807)
Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1443807
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NamenodeJspHelper.java
> 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
> Fix For: 2.0.4-beta
>
> Attachments: hdfs-4471-1.patch, hdfs-4471-2.patch, hdfs-4471-3.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
