[
https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653374#comment-13653374
]
Bikas Saha commented on YARN-392:
---------------------------------
Actually I dont quite get fallThrough :). Fall through what?
bq. I don't think we need to worry about this, an request for a location will
override the previous one, thus an invalid mix cannot happen.
How about this case. Time T1 I make request at priority P1 for specific node N1
in rack R1. So now R1 & * have relaxLocality set to false to prevent allocation
at rack/* for that priority. Now at time T2, if I make a request at priority P1
for specific rack R1. That would require relaxLocality flag to be false only on
*. That is incompatible with the existing flags set. Next case, at T1 I make P1
request for specific node N1 in rack R1. At T2 I make P1 request for
non-specific node N2 in the same rack R1. Now the relaxLocality flag on rack R1
is incompatible for both requests.
bq. I'll add that in. What should we do if the submitted ResourceRequests are
invalid?
Looks like this will be blocked by YARN-394. The only way out of this would be
if we can validate such requests at the time of the allocate RPC itself and
throw an invalidrequest exception. If we cannot do that, and can only find this
out in the scheduling loop then we are blocked on YARN-394.
> 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
