Craig Welch commented on YARN-1994:

FYI, took a look at the changes between patch 3 and 5, it includes support for 
the ApplicationHistory service when an address is specified for it (when one is 
not specified it binds on all ports, but if it is, it won't bind without this 
change).  This impacts ApplicationHistoryClientService.java, 
ApplicationHistoryServer.java, and WebAppUtils.java.  The mapreduce 
configurations where not consolidated when the yarn one was, those are also 
consolidated in the .5 patch.  This impacts JHAdminConfig.java, 
MRWebAppUtil.java, HistoryClientService.java, and HSAdminServer.java.  Some 
redundant logic in AdminService.java was also removed.

> Expose YARN/MR endpoints on multiple interfaces
> -----------------------------------------------
>                 Key: YARN-1994
>                 URL: https://issues.apache.org/jira/browse/YARN-1994
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager, webapp
>    Affects Versions: 2.4.0
>            Reporter: Arpit Agarwal
>            Assignee: Craig Welch
>         Attachments: YARN-1994.0.patch, YARN-1994.1.patch, YARN-1994.2.patch, 
> YARN-1994.3.patch, YARN-1994.4.patch, YARN-1994.5.patch
> YARN and MapReduce daemons currently do not support specifying a wildcard 
> address for the server endpoints. This prevents the endpoints from being 
> accessible from all interfaces on a multihomed machine.
> Note that if we do specify INADDR_ANY for any of the options, it will break 
> clients as they will attempt to connect to We need a solution that 
> allows specifying a hostname or IP-address for clients while requesting 
> wildcard bind for the servers.
> (List of endpoints is in a comment below)

This message was sent by Atlassian JIRA

Reply via email to