FAQ
Hi all,

we have problems to configure the addresses for the webapps of some
services with Cloudera Manager. The problem is that the machine that runs
the ResourceManager and JobHistory Server of YARN has two interfaces, a
private interface (with private IP) for the communication with the other
nodes and a public interface (with public IP) for connections from outside.
The webapps should bind to the public interface in order to be able to
access the web interfaces from outside of the private network. Per default,
all services bind to the private interface which is good in general except
for the webapp services. Unfortunatelly, there is only the possibility to
change the port of the webapps in the Cloudera Manager Configuration but
not the address itself (for what reason?). For the ResourceManager we
managed to get it working by adding the webapp.address property to the
safety valve of the ResourceManager but for the JobHistory Server there is
no such safety valve.
Does anyone has an idea how to configure the webapp addresses for all the
services that have a webapp in general (or at least for the JobHistory
Server in particular)?
We already tried to add the corresponding properties to the config files in
/etc/hadoop/conf (mapred-site.xml and yarn-site.xml) on disk but these
changes are somehow ignored when starting the services with the Cloudera
Manager and the changes to these files are also overwritten when changing
the configuration with the Cloudera Manager.

Thx for any help.

Best regards,
Alex

Search Discussions

  • Vinithra Varadharajan at Oct 24, 2012 at 9:14 pm
    Hi Alexander,

    Cloudera Manager 4.1, which was released today, includes a JobHistory
    safety valve. That would be your best bet to fix this problem.

    I'll file a bug report to make the HTTP UI's hostname configurable for the
    Yarn roles (similar to how it is done for the MapReduce JobTracker).

    -Vinithra
    On Wed, Oct 24, 2012 at 1:57 AM, Alexander Schätzle wrote:

    Hi all,

    we have problems to configure the addresses for the webapps of some
    services with Cloudera Manager. The problem is that the machine that runs
    the ResourceManager and JobHistory Server of YARN has two interfaces, a
    private interface (with private IP) for the communication with the other
    nodes and a public interface (with public IP) for connections from outside.
    The webapps should bind to the public interface in order to be able to
    access the web interfaces from outside of the private network. Per default,
    all services bind to the private interface which is good in general except
    for the webapp services. Unfortunatelly, there is only the possibility to
    change the port of the webapps in the Cloudera Manager Configuration but
    not the address itself (for what reason?). For the ResourceManager we
    managed to get it working by adding the webapp.address property to the
    safety valve of the ResourceManager but for the JobHistory Server there is
    no such safety valve.
    Does anyone has an idea how to configure the webapp addresses for all the
    services that have a webapp in general (or at least for the JobHistory
    Server in particular)?
    We already tried to add the corresponding properties to the config files
    in /etc/hadoop/conf (mapred-site.xml and yarn-site.xml) on disk but these
    changes are somehow ignored when starting the services with the Cloudera
    Manager and the changes to these files are also overwritten when changing
    the configuration with the Cloudera Manager.

    Thx for any help.

    Best regards,
    Alex
  • Alexander Schätzle at Oct 25, 2012 at 2:11 pm
    Hi Vinithra,

    thx for your help. With the JobHistory safety valve in Cloudera Manager 4.1
    we were able to get the JobHistory Web UI working.
    For the future, it would be nice to have a direkt option to change the
    address as well since :-)

    Best regards,
    Alex

    Am Mittwoch, 24. Oktober 2012 23:14:58 UTC+2 schrieb Vinithra:
    Hi Alexander,

    Cloudera Manager 4.1, which was released today, includes a JobHistory
    safety valve. That would be your best bet to fix this problem.

    I'll file a bug report to make the HTTP UI's hostname configurable for the
    Yarn roles (similar to how it is done for the MapReduce JobTracker).

    -Vinithra

    On Wed, Oct 24, 2012 at 1:57 AM, Alexander Schätzle <
    schaetzle...@gmail.com <javascript:>> wrote:
    Hi all,

    we have problems to configure the addresses for the webapps of some
    services with Cloudera Manager. The problem is that the machine that runs
    the ResourceManager and JobHistory Server of YARN has two interfaces, a
    private interface (with private IP) for the communication with the other
    nodes and a public interface (with public IP) for connections from outside.
    The webapps should bind to the public interface in order to be able to
    access the web interfaces from outside of the private network. Per default,
    all services bind to the private interface which is good in general except
    for the webapp services. Unfortunatelly, there is only the possibility to
    change the port of the webapps in the Cloudera Manager Configuration but
    not the address itself (for what reason?). For the ResourceManager we
    managed to get it working by adding the webapp.address property to the
    safety valve of the ResourceManager but for the JobHistory Server there is
    no such safety valve.
    Does anyone has an idea how to configure the webapp addresses for all the
    services that have a webapp in general (or at least for the JobHistory
    Server in particular)?
    We already tried to add the corresponding properties to the config files
    in /etc/hadoop/conf (mapred-site.xml and yarn-site.xml) on disk but these
    changes are somehow ignored when starting the services with the Cloudera
    Manager and the changes to these files are also overwritten when changing
    the configuration with the Cloudera Manager.

    Thx for any help.

    Best regards,
    Alex

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedOct 24, '12 at 8:57a
activeOct 25, '12 at 2:11p
posts3
users2
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase