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 specify hard locality constraints in resource requests
Date Thu, 23 May 2013 18:07:22 GMT

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

Sandy Ryza commented on YARN-392:

bq. Can anyRequest be null. Others are checked for null but this one isn't.
In the contexts that the method is called, it can't be null, but I'll add in a check to be

Will fix the comments as well.

Based on Arun's April 4th comment, my understanding was that capacity scheduler work would
be done in YARN-398. 
> Make it possible to specify hard locality constraints in resource requests
> --------------------------------------------------------------------------
>                 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,
YARN-392-3.patch, YARN-392-4.patch, YARN-392-5.patch, YARN-392-6.patch, YARN-392-7.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