[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619578#comment-13619578
]
Bikas Saha commented on YARN-392:
---------------------------------
Sorry, I did not see that patch carefully and assumed that it does what is
suggested in
https://issues.apache.org/jira/browse/YARN-392?focusedCommentId=13583713&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13583713
whereas it actually implements the proposal in YARN-398.
The typical use case for blacklisting is to disable a set of nodes globally.
e.g. never gives me nodes A and B even when I ask for resources at *. Having to
implement blacklisting by doing it on a per-priority will make the common case
painful to work with. So I am not in favor of such a proposal unless there is a
strong use case for blacklisting on specific priorities. Arun, Vinod and I had
an offline discussion where we agreed that we are better off creating an API
for blacklisting a set of nodes.
> 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
