[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664333#comment-13664333
]
Bikas Saha commented on YARN-392:
---------------------------------
Minor nits
You would want to put ResourceRequest#ANY to be clear what "any" means in the
javadoc.
Can anyRequest be null. Others are checked for null but this one isnt.
Typo in comment. Duplicate non-zero.
{code}
+ return
+ // There must be outstanding requests at the given priority:
+ anyRequest.getNumContainers() > 0 &&
+ // If locality relaxation is turned off at *-level, there must be a
non-zero
+ // non-zero request for the node's rack:
{code}
> 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-5.patch,
> YARN-392-6.patch, YARN-392-7.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
