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-424) Allow resource requests to provide hints to the scheduler
Date Tue, 26 Feb 2013 01:04:15 GMT

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

Bikas Saha commented on YARN-424:
---------------------------------

I agree that being able to extend the API without breaking back-compat is important. I am
+1 for Arun's argument about protobuf's being the right approach to that. There is no need
to add a string or any other hint. Simple add an optional member to the AllocateRequest which
the new scheduler will understand. Other schedulers simply dont know about the new field.
                
> 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

Mime
View raw message