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

Patrick Wendell commented on MAPREDUCE-3451:
--------------------------------------------

We have several pieces of follow-up around this, and one of them can be looking 
at moving SchedulerApp to an interface (this would involve changing the other 
two schedulers as well to some extent).

I'd like to see that change occur in tandem with better documentation for 
common scheduling components like SchedulerApp. The design goals of the RM 
scheduling code are currently opaque to anyone trying to add new code. Better 
documentation would make it clearer how to hook in a new scheduler the right 
way.
                
> Port Fair Scheduler to MR2
> --------------------------
>
>                 Key: MAPREDUCE-3451
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3451
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: mrv2, scheduler
>            Reporter: Patrick Wendell
>            Assignee: Patrick Wendell
>             Fix For: 2.0.1-alpha
>
>         Attachments: MAPREDUCE-3451.v1.patch.txt, 
> MAPREDUCE-3451.v2.patch.txt, MAPREDUCE-3451.v3.patch.txt, 
> MAPREDUCE-3451.v4.patch.txt, MAPREDUCE-3451.v5.patch, 
> MAPREDUCE-3451.v6.patch, MAPREDUCE-3451.v7.patch, MAPREDUCE-3451.v8.patch, 
> MAPREDUCE-3451.v9.patch
>
>
> The Fair Scheduler is in widespread use today in MR1 clusters, but not yet 
> ported to MR2. This is to track the porting of the Fair Scheduler to MR2 and 
> will be updated to include design considerations and progress.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to