You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Matei Dragu (JIRA)" <ji...@apache.org> on 2015/12/02 17:04:10 UTC
[jira] [Commented] (HADOOP-11999)
yarn.resourcemanager.webapp.address and friends are converted to fqdn in
the href urls of the web app.
[ https://issues.apache.org/jira/browse/HADOOP-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036027#comment-15036027 ]
Matei Dragu commented on HADOOP-11999:
--------------------------------------
Hi guys, any update on this issue ? Thanks!
> yarn.resourcemanager.webapp.address and friends are converted to fqdn in the href urls of the web app.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11999
> URL: https://issues.apache.org/jira/browse/HADOOP-11999
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.3.0
> Environment: Linux.
> Reporter: Ewan Higgs
>
> I am setting up a Hadoop cluster where the nodes have FQDNames inside
> the cluster, but the DNS where these names are registered is behind some
> login nodes. So any user who tries to access the web interface needs to
> use the IPs instead.
> I set the 'yarn.nodemanager.webapp.address' and
> 'yarn.resourcemanager.webapp.address' to the appropriate IP:port. I
> don't give it the FQDN in this config field.
> However, when I access the web app it all works inside each web app.
> However, when I cross from the Resource Manager to the Node Manager web
> app, the href url uses the FQDN that I don't want. Obviously this is a
> dead link to the user and can only be fixed if they copy and paste the
> appropriate IP address for the node (not a pleasant user experience).
> I suppose it makes sense to use the FQDN for the link text in the web app, but not the actual url if the IP was specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)