[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654708#comment-13654708
]
Sandy Ryza commented on YARN-392:
---------------------------------
I think the server should check weird requests and state. My point was mainly
that we haven't been doing these checks up to this point, so I didn't think we
should be blocked on it. Especially given that, in this case, the consequences
of invalid requests are for the apps submitting them. There will be no other
bad state inside the RM.
That said, there is some sanity checking that we can do at request time, such
as making sure that if a rack has disableAllocation turned on, the number of
containers requested by nodes under it must sum to at least its number of
containers. I can add this in to the patch.
> 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
