[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653347#comment-13653347
]
Alejandro Abdelnur commented on YARN-392:
-----------------------------------------
'fallThrough' please (even if i cannot pronounce it).
bq. | As discussed earlier in this jira, its not possible to mix strict and
non-strict allocations at the same priority. I dont see that being
checked/enforced anywhere.
bq. I'll add that in. What should we do if the submitted ResourceRequests are
invalid?
I don't think we need to worry about this, an request for a location will
override the previous one, thus an invalid mix cannot happen.
> 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
