[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662302#comment-13662302
]
Sandy Ryza commented on YARN-392:
---------------------------------
The crisp definition I had in mind was: "if disableAllocation=true for a
ResourceRequest, don't use that ResourceRequest by itself for an allocation."
The alternative is "if disableAllocation=true for a ResourceRequest at a
network hierarchy level, then do not relax locality beyond that level." I
think both of these are crisp, and I would be ok with both of them. How about:
I remove that line in the scheduler that honors the property on node-level
requests. We document that the flag is not supported on node-level requests.
If we wish to, in a followup JIRA we can decide that setting the flag on a
node-level request warrants an exception. Or, in a followup JIRA, we can
decide that setting the flag on a node-level request is supported. Neither of
these future changes will be a backwards-incompatible change.
> Make it possible to specify hard locality constraints in resource requests
> --------------------------------------------------------------------------
>
> 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-3.patch, YARN-392-4.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
