[
https://issues.apache.org/jira/browse/MAPREDUCE-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joydeep Sen Sarma updated MAPREDUCE-2047:
-----------------------------------------
Attachment: 2047.3.patch
added some additional small optimizations to reduce JT lock critical section
and fixed a bug. hadoopQA output:
[exec] BUILD SUCCESSFUL
[exec] Total time: 1 minute 17 seconds
[exec]
[exec]
[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
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec] +1 system tests framework. The patch passed system tests
framework compile.
[exec]
[exec]
[exec]
[exec]
[exec]
======================================================================
[exec]
======================================================================
[exec] Finished build.
[exec]
======================================================================
[exec]
======================================================================
> reduce overhead of findSpeculativeTask
> --------------------------------------
>
> Key: MAPREDUCE-2047
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2047
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Environment: hadoop-20 with HADOOP-2141
> Reporter: Joydeep Sen Sarma
> Assignee: Joydeep Sen Sarma
> Attachments: 2047.3.patch, mapreduce-2047.1.patch,
> mapreduce-2047.2.patch
>
>
> We are bottlenecked (in the JT) on the jobtracker lock and calls to
> findSpeculativeTask frequently show up as one of the top routines (by time)
> called holding this lock.
> this routine calls canBeSpeculated() and hasRunOnMachine() for each task in a
> candidate job. Both these routines are reasonably expensive when invoked
> repeatedly for thousands of tasks. The top candidates for speculation from a
> job only need to be refreshed periodically (and not once every heartbeat) -
> and we can can avoid most of these invocations this way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
