[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661513#comment-13661513
]
Bikas Saha commented on YARN-392:
---------------------------------
I am not sure how we are making the semantics consistent by overloading
something for 2 things. When the flag is set at a network hierarchy level then
it means then scheduler will not relax locality beyond that level. The same
flag can also be used to blacklist locations.
The most common use case of black listing is to specify a set of nodes on which
no allocations should be made (eg they are badly behaving nodes). How does this
scheme address that case? Will we have to specify the same blacklist
information for every priority that is used by an application (because resource
request is per priority). Every time an app uses a new priority we will have to
issue a new set of resource requests to blacklist at that priority?
> 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
