[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576322#comment-13576322
]
Sandy Ryza commented on YARN-392:
---------------------------------
Agreed that we should discuss before committing to an approach. The first
approach that comes to my mind would be to have a boolean flag with each
resource request that says whether or not it's ok to schedule it somewhere
else. An issue with this is that it would be impossible to make a request like
"I want a container to be only on one of these two nodes".
Also agreed that this and YARN-393 are closely tied together, so I'd be happy
to take on both if that ends up making the most sense.
> 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
>
> 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
