[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661767#comment-13661767
]
Sandy Ryza commented on YARN-392:
---------------------------------
We currently have a working patch that has gone through multiple phases of
review. This patch implements the proposal made by Arun on YARN-398, which
many comments led me to believe we had consensus on. The approach enables
whitelisting by setting a disable-allocation flag on certain requests, so some
form of "blacklisting" is a natural extension of it. The changes to the
scheduler are about 10 lines. Modifying the proposal to support *only*
whitelisting would require many additional changes, and do nothing to simplify
the current changes.
As I said, if everyone else participating agrees on these additional changes, I
am happy to implement them. But my opinion is that the best way to get this
into 2.0.5, both in terms of soundness of the approach and in terms of
punctuality, is to go with what we have worked on so far.
> 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
