[
https://issues.apache.org/jira/browse/HADOOP-8804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins reassigned HADOOP-8804:
-----------------------------------
Assignee: Senthil V Kumar (was: Vinay)
Hi Senthil,
Not sure we want to use the hostname since presumably that's already in the URL
bar. Ie we're getting additional info (the RPC address and port).
Some options:
- We just have "NameNode (active)", eg remove the IP:port
- We use the NN hostname's IP and RPC port
- We use the logical NN id (eg dfs.ha.namenodes.nameserviceId1.nn1) from the
config
- We leave as is because it's useful to indicate RPC is bound to the wildcard
Btw noticed you're patch is using tabs/4 spaces. Please checkout for the style
guide:
http://wiki.apache.org/hadoop/HowToContributeAlso please don't re-org all the
import statements in this change.
Thanks,
Eli
> 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
> Assignee: Senthil V Kumar
> 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
