You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/04/15 00:44:18 UTC

[jira] [Updated] (TEZ-1053) Refactor: Pass TaskLocationHint directly to the Scheduling logic

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

Bikas Saha updated TEZ-1053:
----------------------------

    Attachment: TEZ-1053.1.patch

Straight-forward refactoring. The TaskLocationHint is now passed from the TaskAttemptImpl to the TaskSchedulerEventHandler.

> Refactor: Pass TaskLocationHint directly to the Scheduling logic
> ----------------------------------------------------------------
>
>                 Key: TEZ-1053
>                 URL: https://issues.apache.org/jira/browse/TEZ-1053
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: TEZ-1053.1.patch
>
>
> Currently, the location hint is resolved and translated to hosts and relaxed to racks directly in the TaskAttemptImpl code. The AMRMClient already does that and so we are duplicating the name resolution and relaxation of host->rack. Also, as the information in TaskLocationHint evolves further, eg. support for container locality, then its better to leave the bindings as late as possible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)