[
https://issues.apache.org/jira/browse/MAPREDUCE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966349#action_12966349
]
Joydeep Sen Sarma commented on MAPREDUCE-2118:
----------------------------------------------
Scott - looks like this has been running without glitch on the production
cluster for the last two weeks! So seems safe to review/commit at this point.
> optimize getJobSetupAndCleanupTasks
> ------------------------------------
>
> Key: MAPREDUCE-2118
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2118
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Joydeep Sen Sarma
> Assignee: Joydeep Sen Sarma
> Attachments: mapreduce-2118.1.patch
>
>
> in every heartbeat, while holding the JobTracker global lock, all jobs are
> scanned for job setup/cleanup, task setup/cleanup. on a large system with
> many trackers (and heartbeats) and many jobs - this becomes the bottleneck
> for JT throughput.
> One possible route may be to rework the code to not require the JT lock while
> asking the JIP whether it has a setup/cleanup task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
