[
https://issues.apache.org/jira/browse/MAPREDUCE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412941#comment-13412941
]
Patrick Wendell commented on MAPREDUCE-3451:
--------------------------------------------
Hey Arun - I think extending it is a better move for now.
If we decided to move SchedulerApp to an interface, 95% of the implementation
would be the same between the FS/CS. The only differences are in the way delay
scheduling works for the FairScheduler.
As far as I can tell - the idea behind SchedulerApp is to deal with application
lifecycle management from the perspective of the scheduler. That's helpful to
have and made writing the FS simpler. This is likely to be useful for future
schedulers well. In terms of maximizing code sharing I would be in favor of
keeping it collectively managed.
> 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
> 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
>
>
> 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
