[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654993#comment-13654993
]
Sandy Ryza commented on YARN-392:
---------------------------------
For YARN-394, the case you mentioned in which a high memory machine is lost is
the one I was thinking of. Adding it to the JIRA description. Filed YARN-664
for the same-priority, different-capability case.
Sorry to keep vacillating on this, but, in the fair scheduler at least, I don't
think it makes sense to include the check for high #containers on requests with
disableAllocation. It requires a new data structure that maps racks to nodes
and checks for all the nodes on a rack with each allocation. I think this is
an unnecessary performance hit. I did, however, add in a safeguard to make
sure that disabling locality on an existing request won't leave around
unsatisfiable reservations, so it shouldn't be possible for an app's mistakes
to result in any inconsistent RM state.
bq. So you may want to check with Arun C Murthy if the intent of that jira
matches what you think it is.
On a comment here on April 4, Arun mentioned that he would be happy to
repurpose it. If this is no longer the case, I'd be happy to file a new JIRA,
but I don't feel confident in my knowledge of the capacity scheduler to make
the right changes for it.
I'm uploading a new patch that includes the name change to disableAllocation,
the test Bikas asked for related to cancelling strict locality, and a few other
fixups.
> 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.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
