hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality
Date Thu, 09 May 2013 21:03:18 GMT

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

Sandy Ryza commented on YARN-392:

Disable-node allows you to say "I specifically don't want a container on this node".  I can't
speak to whether this is a useful feature, but it makes the semantics consistent in the sense
that the flag can simply mean "don't directly use this ResourceRequest for an allocation".

If we allow Disable-node, I like disableAllocation as the name.  Otherwise, fallThrough or
relaxLocality both seem good to me.

bq. The two checks seem to be different. One checks for containers > 0 while the other
does not. Dont know if that matters in the fair scheduler?
This is correct behavior, according to the way I was envisioning it.  If we hit a disableAllocation
flag, we want to abort trying to allocate this node/priority to the app entirely.  On the
other hand, if the node/rack has 0 requests, we want to fall through to the next level.  I'll
try to see if there's a clearer way to structure the code.

bq. As discussed earlier in this jira, its not possible to mix strict and non-strict allocations
at the same priority.  I dont see that being checked/enforced anywhere.
I'll add that in.  What should we do if the submitted ResourceRequests are invalid? 

Capacity scheduler changes are targeted for YARN-398.
> Make it possible to schedule to specific nodes without dropping locality
> ------------------------------------------------------------------------
>                 Key: YARN-392
>                 URL: https://issues.apache.org/jira/browse/YARN-392
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Sandy Ryza
>         Attachments: YARN-392-1.patch, YARN-392-2.patch, YARN-392-2.patch, YARN-392-2.patch,
> Currently its not possible to specify scheduling requests for specific nodes and nowhere
else. The RM automatically relaxes locality to rack and * and assigns non-specified machines
to the app.

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