[
https://issues.apache.org/jira/browse/MAPREDUCE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413457#comment-13413457
]
Arun C Murthy commented on MAPREDUCE-3451:
------------------------------------------
bq. As far as I can tell - the idea behind SchedulerApp is to deal with
application lifecycle management from the perspective of the scheduler.
I wish I had a chance to respond to Patrick before this was committed... IAC,
we should plan to allow the schedulers to deviate in significant ways (which is
the whole point of having multiple schedulers) and, as a result, minimizing
interference is a key goal.
Maybe we should open a jira to make SchedulerApp an interface?
I originally kept it common across FifoScheduler and CapacityScheduler since,
for the degenerate case of a single queue, they are identical (currently) and
planned to pull it out as a separate one once they deviated.
> 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
