[
https://issues.apache.org/jira/browse/MAPREDUCE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Peterson updated MAPREDUCE-698:
-------------------------------------
Attachment: mapreduce-698-trunk-3.patch
changes from previous patch:
- extra newline in fairscheduler.java removed
- removed "single test" changes from build-contrib.xml (they didn't accomplish
what I wanted -- to run just a single test method)
- Regarding checkAssignment, I made the change you suggested, but I'm not sure
I'm testing things in the best way. The only thing I'm concerned with is that
it ends up scheduling the right number from each pool, the only way I was able
to get it to actually assign the jobs was to use checkAssignment.
- in the UI, labels are "Max Share"
- Removed Pool.numRunningTasks since it was only used from within
PoolSchedulable, where this data is already available.
- Moved cap from getDemand() to updateDemand().
- Documentation updated
- Removed tabs.
> Per-pool task limits for the fair scheduler
> -------------------------------------------
>
> Key: MAPREDUCE-698
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-698
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: contrib/fair-share
> Reporter: Matei Zaharia
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-698-prelim.patch, mapreduce-698-trunk-3.patch,
> mapreduce-698-trunk.patch, mapreduce-698-trunk.patch
>
>
> The fair scheduler could use a way to cap the share of a given pool similar
> to MAPREDUCE-532.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
