[
https://issues.apache.org/jira/browse/MAPREDUCE-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934065#action_12934065
]
Ramkumar Vadali commented on MAPREDUCE-1783:
--------------------------------------------
Latest patch TEST RESULTS:
One test fails, but that also fails on a clean checkout
{code}
[junit] Test org.apache.hadoop.mapred.TestControlledMapReduceJob FAILED
(timeout)
{code}
ant test-patch succeeds:
{code}
[exec]
[exec]
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
(version 1.3.9) warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec] +1 system test framework. The patch passed system test
framework compile.
[exec]
[exec]
[exec]
[exec]
[exec]
======================================================================
[exec]
======================================================================
[exec] Finished build.
[exec]
======================================================================
[exec]
======================================================================
[exec]
[exec]
BUILD SUCCESSFUL
Total time: 13 minutes 6 seconds
Test results are in /tmp/rvadali.hadoopQA
{code}
> Task Initialization should be delayed till when a job can be run
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-1783
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1783
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/fair-share
> Affects Versions: 0.20.1
> Reporter: Ramkumar Vadali
> Assignee: Ramkumar Vadali
> Fix For: 0.22.0
>
> Attachments: 0001-Pool-aware-job-initialization.patch,
> 0001-Pool-aware-job-initialization.patch.1, MAPREDUCE-1783.patch,
> submit-mapreduce-1783.patch
>
>
> The FairScheduler task scheduler uses PoolManager to impose limits on the
> number of jobs that can be running at a given time. However, jobs that are
> submitted are initiaiized immediately by EagerTaskInitializationListener by
> calling JobInProgress.initTasks. This causes the job split file to be read
> into memory. The split information is not needed until the number of running
> jobs is less than the maximum specified. If the amount of split information
> is large, this leads to unnecessary memory pressure on the Job Tracker.
> To ease memory pressure, FairScheduler can use another implementation of
> JobInProgressListener that is aware of PoolManager limits and can delay task
> initialization until the number of running jobs is below the maximum.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
