hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality
Date Fri, 10 May 2013 20:35:16 GMT

    [ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654806#comment-13654806
] 

Bikas Saha commented on YARN-392:
---------------------------------

bq. My point was mainly that we haven't been doing these checks up to this point, so I didn't
think we should be blocked on it. 
Would be great if you could help enumerate cases you know of. We can add them to YARN-394
for tracking.

Recently, we started throwing InvalidResourceRequest in the RM for requests that are invalid
(more than max resource allowed etc) in YARN-193. So that takes care of one of the known cases
where checks were not being performed. The other case is when a Resource request is valid
but later becomes invalid mainly related to nodes being lost. E.g. when a high memory machine
is lost. Or when specific resources were requested (this jira) and they become unavailable
later on. These cases motivated YARN-394 and are described therein. So we are tracking towards
sanity checking IMO. In YARN-142 etc we are changing protocols so that such exceptions are
visible to users and they can act on them programmatically.

bq. Capacity scheduler changes are targeted for YARN-398.
The title of that jira says white listing and black listing of nodes. So you may want to check
with [~acmurthy] if the intent of that jira matches what you think it is.
                
> 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

Mime
View raw message