hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matei Dragu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11999) yarn.resourcemanager.webapp.address and friends are converted to fqdn in the href urls of the web app.
Date Wed, 02 Dec 2015 16:26:11 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036066#comment-15036066
] 

Matei Dragu commented on HADOOP-11999:
--------------------------------------

[~ehiggs] thank you for the quick reply but now I realised that I might have misunderstood
the bug contents. 

I am experiencing the following problem: 
If I set the yarn.nodemanager.webapp.address property one a node as HOST:PORT, in the GUI
of the ResourceManager that node registered with that setting is ignored in the nodes list.
Instead the yarn.nodemanager.webapp.address, the URL displayed in the Node HTTP Address column
is {yarn.manager.hostname}:PORT

Example:
If yarn.nodemanager.webapp.address is set to mywebhost:1234 and yarn.manager.hostname is set
to mynodehost, the node will appear as mynodehost:1234 in the web GUI.

Is this a known behavior ?

YARN Version I am using: 2.6.0-cdh5.5.0

Thank you in advance!

> 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)

Mime
View raw message