You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/11/23 12:01:02 UTC

[jira] [Updated] (MAPREDUCE-7070) Batch calls to RackResolver from AM

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

Sunil Govindan updated MAPREDUCE-7070:
--------------------------------------
    Target Version/s: 3.3.0  (was: 2.6.6, 3.2.0)

Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker.

> Batch calls to RackResolver from AM
> -----------------------------------
>
>                 Key: MAPREDUCE-7070
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7070
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster, performance
>            Reporter: Greg Phillips
>            Priority: Minor
>         Attachments: MAPREDUCE-7070.patch
>
>
> TaskAttemptImpl calls RackResolver once for every split location. This results in many shells being spawned by the Application Master when the topology script is enabled. The worst case scenario would entail one call to the topology script for each Datanode. The NameNode is also topology aware, and uses batch calls to the topology script to improve performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org