[
https://issues.apache.org/jira/browse/HADOOP-8804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senthil V Kumar updated HADOOP-8804:
------------------------------------
Attachment: HADOOP-8804-trunk.patch
HADOOP-8804-1.0.patch
I was able to fix this issue by getting the hostname when the configuration has
a wildcard IP address. Hadoop 1.0.4 required change in namenode and job
tracker. So uploading a different patch. Let me know whether the approach is
correct. Hadoop 1.0.4 is not allowing wildcard IPs for fs.default.name, so I
wasn't able to test it.
I couldn't assign the JIRA to myself, can you assign this JIRA to me.
> Improve Web UIs when the wildcard address is used
> -------------------------------------------------
>
> Key: HADOOP-8804
> URL: https://issues.apache.org/jira/browse/HADOOP-8804
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Eli Collins
> Priority: Minor
> Labels: newbie
> Attachments: HADOOP-8804-1.0.patch, HADOOP-8804-trunk.patch
>
>
> When IPC addresses are bound to the wildcard (ie the default config) the NN,
> JT (and probably RM etc) Web UIs are a little goofy. Eg "0 Hadoop Map/Reduce
> Administration" and "NameNode '0.0.0.0:18021' (active)". Let's improve them.
--
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
