[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662067#comment-13662067 ]
Alejandro Abdelnur commented on YARN-392: ----------------------------------------- [~ bikassaha], as [~sandyr] points out, blacklisting is a natural consequence of whitelisting and viceversa. The driver of this JIRA is to enable specific node/rack allocation. This is achieved, leveraging the existing protocol/scheduler semantics via a blacklisting of the rack and ALL. As we use the same type of request for node/rack/ALL, doing the blacklisting in the node comes as a freebie, not an intended one. In this case, the AM is the one that decides to do the node blacklisting, it has nothing to do with the health of the node (still, it is the RM's responsibility to take care of this). >From my end, I don't have an immediate use of app node blacklisting. And Sandy >indicates that modifying the scheduler not to handle node blackisting it will >require additional changes. If this is a concern, we could do that as a sanity >check in the RM when resource requests arrive (if I recall correctly, there is >a JIRA for this, I've done a quick search, but I could not find it). > 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