[jira] [Updated] (MAPREDUCE-6117) Hadoop ignores yarn.nodemanager.hostname for RPC listeners

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated MAPREDUCE-6117:
----------------------------------------
    Labels: BB2015-05-TBR  (was: )

> Hadoop ignores yarn.nodemanager.hostname for RPC listeners
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-6117
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6117
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, task
>    Affects Versions: 2.2.1, 2.4.1, 2.5.1
>         Environment: Any mapreduce example with standard cluster.  In our case each node has four networks.  It is important that all internode communication be done on a specific network.
>            Reporter: Waldyn Benbenek
>            Assignee: Waldyn Benbenek
>              Labels: BB2015-05-TBR
>             Fix For: 2.5.1
>
>         Attachments: MapReduce-534.patch
>
>   Original Estimate: 48h
>          Time Spent: 384h
>  Remaining Estimate: 0h
>
> The RPC listeners for an application are using the hostname of the node as the binding address of the listener,  They ignore yarn.nodemanager.hostname for this.  In our setup we want all communication between nodes to be done via the network addresses we specify in yarn.nodemanager.hostname on each node.  
> TaskAttemptListenerImpl.java and MRClientService.java are two places I have found where the default address is used rather that NM_host.   The node Manager hostname should be used for all communication between nodes including the RPC listeners.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)