hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-424) Allow resource requests to provide hints to the scheduler
Date Mon, 25 Feb 2013 16:10:16 GMT

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

Alejandro Abdelnur commented on YARN-424:

Regarding the format/type for hints, while using 16 bytes would do, I'd prefer to use something
that does not require having to deal with byte masking. While chatting about this, Bikas suggested
a byte[], that woud be certainly much better. Still, I think having a capped String (50 or
100 chars) would something much easier to deal with the plus that printing a hint in the logs
would be straight forward. 

My take is that hints should be a comma separated list of key/values or values

* KEY -> word
* VALUE -> word

> 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