[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660946#comment-13660946
]
Sandy Ryza commented on YARN-392:
---------------------------------
We are implementing the approach outlined by Arun in his first comment on
YARN-398. Although it is not the primary goal, the approach does allow for
node/rack blacklisting, and loses nothing by doing so. Even if we were to say
that you can't set the disable-allocation flag on node-level requests, it would
still be possible to blacklist racks by setting the disable flag on a rack and
submitting node requests for nodes under it. It would also still be possible
to blacklist nodes by whitelisting every other node on its rack. Allowing the
disable-allocation flag on node-level requests just makes the semantics more
consistent.
I'll update the title of the JIRA to better reflect this.
> 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-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
