tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-344) Add an option to allow node-local only scheduling in the TaskScheduler
Date Tue, 06 Aug 2013 21:52:47 GMT

    [ https://issues.apache.org/jira/browse/TEZ-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731346#comment-13731346

Bikas Saha commented on TEZ-344:

No the RM will not assign 2 containers for the same resource request unless the racks are
also common. If the racks are common and it does it, then getMatchingRequests() will not returning
any match for container on host2 (assuming host1 container already matched T1 or vice versa).
In that case, the TaskScheduler will release the container back to the RM. That I think is
the intent of this jira too.

I wrote the TaskScheduler with the design intentions of working closely with YARN and not
working around YARN. If there have been issues in YARN I have fixed those so that YARN works
for everyone and the TaskScheduler is a model piece of code on how to interact with correctly
with YARN. I am wary of adding additional delay logic in the TaskScheduler. This is like adding
more sleep in a call stack to make things somehow work. Thats not the philosophy of the TaskScheduler
> Add an option to allow node-local only scheduling in the TaskScheduler
> ----------------------------------------------------------------------
>                 Key: TEZ-344
>                 URL: https://issues.apache.org/jira/browse/TEZ-344
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>              Labels: TEZ-0.2.0
> This, for now, is primarily to help with testing of Tez on clusters.
> Would have to go in with a warning since this could cause jobs to hang / run for a long
> Longer term, this can be enhanced to set limits on how long to wait before assigning
non-local tasks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message