[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618475#comment-13618475
]
Bikas Saha commented on YARN-392:
---------------------------------
How about calling is disableLocalityRelaxation as thats what it is basically
doing. When specified on a node it would mean do not relax locality to rack or
ANY. Potentially, we could also say that when specified on a rack then it would
mean do not relax locality to ANY. Do you think it could be used to specify
either exact nodes or exact racks. In that case, we would need to check that if
this flag is set then either nodes or racks but not both are specified.
I am not sure how to make sense of 2 different asks to the RM (at the same
priority) that say
1) allocate at specific node A (ie do not relax locality to rackA)
2) allocate at specific rack rackA (ie do not relax locality to ANY) where node
A is contained in rackA
> 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.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
