Great, I am building nightly off of trunk and will try a snapshot version.
This also worked for me;
sh /var/lib/ambari-server/resources/scripts/configs.sh -u admin -p admin -port 
8081 set localhost c1 hdfs-site dfs.namenode.http-address 0.0.0.0:50070
Thanks,
Mike


From: Yusaku Sako <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Thursday, December 12, 2013 at 1:27 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: core-site.xml -> dfs.namenode.http-address bind to 0.0.0.0

Hi Michael,

Ambari 1.4.1 and earlier did not allow the user to specify
dfs.namenode.http-address (aka dfs.http.address).
In Ambari 1.4.2 (which is being finalized as we speak), will expose
dfs.namenode.http-address via the HDFS > Configs page.
You can set it to 0.0.0.0:50070 there.

Hope this helps.

Yusaku

On Thu, Dec 12, 2013 at 11:22 AM, Harp, Michael
<[email protected]<mailto:[email protected]>> wrote:
While that may be true in a general sense it does not work when you have
multiple nics. We have a high speed network for all the hadoop ipc using
FQDN and slow 10G that is on the customer site lan.
Mike

From: Vinod Kumar Vavilapalli <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Thursday, December 12, 2013 at 11:10 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: core-site.xml -> dfs.namenode.http-address bind to 0.0.0.0

dfs.namenode.http-address is supposed to be a user visible address. So FQDN
is a better config.

Thanks,
+Vinod Kumar Vavilapalli
Hortonworks Inc.
http://hortonworks.com/


On Dec 12, 2013, at 10:58 AM, Harp, Michael 
<[email protected]<mailto:[email protected]>>
wrote:

Using ambari 1.4.1.25, is there a way I can bind to 0.0.0.0 instead of the
FQDN? Seems that many of the services are already defaulting to 0.0.0.0 but
not dfs.namenode.http-address?
Thanks,
Mike



CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader of
this message is not the intended recipient, you are hereby notified that any
printing, copying, dissemination, distribution, disclosure or forwarding of
this communication is strictly prohibited. If you have received this
communication in error, please contact the sender immediately and delete it
from your system. Thank You.

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

Reply via email to