You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-user@hadoop.apache.org by Ewan Higgs <ew...@ugent.be> on 2015/05/19 17:09:15 UTC
Web Address appears to be ignored
Hi all,
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).
Is there a way to convince the web app to not use the FQDN or is this a
potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
Yours,
Ewan
Re: Web Address appears to be ignored
Posted by Ewan Higgs <ew...@ugent.be>.
Thanks for the feedback Ravi. I entered a JIRA:
https://issues.apache.org/jira/browse/HADOOP-11999
-Ewan
On 05/19/2015 07:45 PM, Ravi Prakash wrote:
> Ewan!
>
> This sounds like a bug. Please open a JIRA.
>
> Thanks
> Ravi
>
>
>
> On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
>
>
> Hi all,
> 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).
>
> Is there a way to convince the web app to not use the FQDN or is this a
> potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
>
> Yours,
> Ewan
>
>
Re: Web Address appears to be ignored
Posted by Ewan Higgs <ew...@ugent.be>.
Thanks for the feedback Ravi. I entered a JIRA:
https://issues.apache.org/jira/browse/HADOOP-11999
-Ewan
On 05/19/2015 07:45 PM, Ravi Prakash wrote:
> Ewan!
>
> This sounds like a bug. Please open a JIRA.
>
> Thanks
> Ravi
>
>
>
> On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
>
>
> Hi all,
> 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).
>
> Is there a way to convince the web app to not use the FQDN or is this a
> potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
>
> Yours,
> Ewan
>
>
Re: Web Address appears to be ignored
Posted by Ewan Higgs <ew...@ugent.be>.
Thanks for the feedback Ravi. I entered a JIRA:
https://issues.apache.org/jira/browse/HADOOP-11999
-Ewan
On 05/19/2015 07:45 PM, Ravi Prakash wrote:
> Ewan!
>
> This sounds like a bug. Please open a JIRA.
>
> Thanks
> Ravi
>
>
>
> On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
>
>
> Hi all,
> 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).
>
> Is there a way to convince the web app to not use the FQDN or is this a
> potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
>
> Yours,
> Ewan
>
>
Re: Web Address appears to be ignored
Posted by Ewan Higgs <ew...@ugent.be>.
Thanks for the feedback Ravi. I entered a JIRA:
https://issues.apache.org/jira/browse/HADOOP-11999
-Ewan
On 05/19/2015 07:45 PM, Ravi Prakash wrote:
> Ewan!
>
> This sounds like a bug. Please open a JIRA.
>
> Thanks
> Ravi
>
>
>
> On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
>
>
> Hi all,
> 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).
>
> Is there a way to convince the web app to not use the FQDN or is this a
> potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
>
> Yours,
> Ewan
>
>
Re: Web Address appears to be ignored
Posted by Ravi Prakash <ra...@ymail.com>.
Ewan!
This sounds like a bug. Please open a JIRA.
ThanksRavi
On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
Hi all,
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).
Is there a way to convince the web app to not use the FQDN or is this a
potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
Yours,
Ewan
Re: Web Address appears to be ignored
Posted by Ravi Prakash <ra...@ymail.com>.
Ewan!
This sounds like a bug. Please open a JIRA.
ThanksRavi
On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
Hi all,
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).
Is there a way to convince the web app to not use the FQDN or is this a
potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
Yours,
Ewan
Re: Web Address appears to be ignored
Posted by Ravi Prakash <ra...@ymail.com>.
Ewan!
This sounds like a bug. Please open a JIRA.
ThanksRavi
On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
Hi all,
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).
Is there a way to convince the web app to not use the FQDN or is this a
potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
Yours,
Ewan
Re: Web Address appears to be ignored
Posted by Ravi Prakash <ra...@ymail.com>.
Ewan!
This sounds like a bug. Please open a JIRA.
ThanksRavi
On Tuesday, May 19, 2015 8:09 AM, Ewan Higgs <ew...@ugent.be> wrote:
Hi all,
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).
Is there a way to convince the web app to not use the FQDN or is this a
potential bug? Or maybe this will end up as "WONTFIX - open up your DNS".
Yours,
Ewan