Craig Welch commented on YARN-1994:

-re [~arpitagarwal] comments - [~mipoto] made the changes along the lines of 
those requested to AdminService.java in p5, the application master, client rm, 
history client, resource localization and resource tracker services all have 
changes to support the bind properties - I think in some cases the file names 
are different, but the services look to be covered - I changed WebAppUtils to 
use RPCUtil as suggested, TIMELINE_SERVICE_BIND_HOST was used by Milan in p5 
when he added support for that service.  I am attaching a .6 patch, which 
consists of Milan's .5 patch with the change to WebAppUtils to use RPCUtil, and 
a change to add a separate getRMWebAppBindURLWithoutScheme() method, to make 
sure there is no confusion about it's purpose, I returned 
getRMWebAppURLWithoutScheme() to it's earlier functionality, in case it is used 
by external code, so it will work properly (it should not have the bind logic). 
 All relatively small changes, but look to be worthwhile finishing.  In my 
interactive testing everything looks to be working properly.  [~arpitagarwal] 
(and [~mipoto], if you like), can you take one more quick look?

> 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-1994.6.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