[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622558#comment-13622558
]
Arun C Murthy commented on YARN-392:
------------------------------------
[~bikassaha] I'm against using timers for specifying locality delays - it
doesn't make sense for a variety of reasons documented elsewhere.
----
[~sandyr] I just uploaded a patch I lost track of for a week or so on YARN-398.
Looks like we both are doing the same thing. I'm happy to repurpose one of the
two jiras for CS while the other can do the same for FS. Makes sense?
In my patch I called the flag as 'strictLocality' which defaults to 'false'.
That should solve the need for white-lists. Makes sense?
----
I agree we should tackle black-listing separately.
> 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
