[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576299#comment-13576299
]
Bikas Saha commented on YARN-392:
---------------------------------
Since you have already gone ahead and assigned it to yourself, why dont you
take a shot.
If YARN-393 gets solved then my guess is that this jira might get automatically
resolved. However, YARN-393 is even more complex and potentially hard to fix.
It would be good if you can post your ideas/approach first instead of a patch.
This jira might be tricky and so discussing alternatives and agreeing on one of
them would be a good exercise. I will try to post an alternative to this jira
too.
> 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
