[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654655#comment-13654655
]
Bikas Saha commented on YARN-392:
---------------------------------
Of course, changing the AMRMClient to support this would be a logical extension.
Does that mean that the server can afford to not check for inconsistent
requests that will result in a bad state for the server and/or incorrect
results for the users? Perhaps only when AMRMClient is the only entity that is
ever going to talk to the server. Is that the case? Not doing checks by
assuming that pre-conditions will hold is a slippery path IMO.
Currently, when ApplicationMasterService calls scheduler.allocate then the
scheduler can throw an exception about invalid allocations which get returned
to the client. So its fairly easy to solve this in YARN-394.
> 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-2.patch, YARN-392-2.patch,
> YARN-392-2.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
