[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662326#comment-13662326
]
Arun C Murthy commented on YARN-392:
------------------------------------
bq. The alternative is "if disableAllocation=true for a ResourceRequest at a
network hierarchy level, then do not relax locality beyond that level."
This is exactly what YARN-398 does too.
I buy Bikas's argument that blacklist should be separate from whitelist and it
shouldn't be per ResourceRequest.
> 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
