hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler
Date Tue, 26 Feb 2013 00:38:13 GMT

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

Arun C Murthy commented on YARN-424:

I'm not a fan of stringly-typed 'features' in the Scheduler.

We should focus on actual use-cases and come up with well thought out solutions to those -
MapReduce configuration is a very good example of how using key/value pairs leads us down
to crazy nooks and corners.

Gang-scheduling, deadline-scheduling etc. are core-features in the scheduler, and should be
treated as such i.e. we should explicitly support them in the protocol - not as string hints.
> Allow resource requests to provide hints to the scheduler 
> ----------------------------------------------------------
>                 Key: YARN-424
>                 URL: https://issues.apache.org/jira/browse/YARN-424
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: api, applications, scheduler
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
> As initially discussed on YARN-392, it would be helpful for the allocate protocol to
be able to include hints to the scheduler.  Examples hints could include deadlines (containers
needed by a certain time) or gangs (resources that should be scheduled at the same time or
not at all).
> To avoid placing complex scheduling expectations on the RM, the restrictions on hints
would be:
> * Any scheduler may ignore any subset of hints. That is, applications must be written
to handle resource requests as if their hints don't exist.
> * Must be bounded in length - perhaps no larger than 16 bytes or 100 characters.

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

View raw message