[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616917#comment-13616917
]
Sandy Ryza commented on YARN-392:
---------------------------------
Uploading a patch based on the earlier discussion here and on YARN-398. The
patch adds a boolean flag to each resource request which essentially means
"don't schedule using this resource request or any above it" and adds support
for it to the fair scheduler. I call the flag "noAllocateAt", but we could
definitely use a better name if anybody has suggestions. I didn't use
"blacklist" because it already has a meaning in the context of mapreduce, and
to me seems to imply that a blacklisted rack would not allow any containers to
be scheduled anywhere on it, when the meaning is a little different.
> 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
