You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Scott Chen (JIRA)" <ji...@apache.org> on 2011/01/05 01:24:48 UTC
[jira] Commented: (MAPREDUCE-2118) optimize
getJobSetupAndCleanupTasks
[ https://issues.apache.org/jira/browse/MAPREDUCE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977549#action_12977549 ]
Scott Chen commented on MAPREDUCE-2118:
---------------------------------------
We have been running this for a while with no problem.
+1 The patch looks good to me. Can we remove this dead comment?
{code}
+ // jobtracker.createTaskEntry(taskid, taskTracker, this);
{code}
> 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.