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, 04 Apr 2013 20:54:16 GMT

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

Sandy Ryza commented on YARN-392:

[~acmurthy], that makes sense to me.  We can use this one for FS and YARN-398 for CS?  Do
you think this should go into FIFO as well?
[~bikassaha], if we went with your proposal, would it not make sense to go with the convention
used in the FS/CS already, in which the locality delay is a fraction of the cluster size?
 In your proposal, if I want a node-local container at node1, would I specify the locality
delay on the request for node1 or on the request for the rack that node1 is on?
> 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.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