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:55:14 UTC

[jira] [Resolved] (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 resolved TEZ-1053.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 0.5.0

commit dbbb7a217be4a26e71b8e410aa66796c5c3096f1
Author: Bikas Saha <bi...@apache.org>
Date:   Mon Apr 14 15:51:09 2014 -0700

    TEZ-1053. Refactor: Pass TaskLocationHint directly to the Scheduling logic (bikas)


> 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
>             Fix For: 0.5.0
>
>         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)