[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joydeep Sen Sarma updated MAPREDUCE-2118:
-----------------------------------------

    Assignee: Joydeep Sen Sarma
      Status: Patch Available  (was: Open)

> 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.

Reply via email to