[
https://issues.apache.org/jira/browse/MAPREDUCE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832468#action_12832468
]
Amar Kamat commented on MAPREDUCE-1354:
---------------------------------------
Job initialization (job.split localization) can also take up considerable
amount of time. Hence we should avoid access to any getter calls to
JobInProgress while the initialization is in progress. Following are the other
methods that first lock the JobTracker and then JobInProgress potentially
locking up the JobTracker during the job initialization.
- getMapTaskReports()
- getReduceTaskReports()
- getCleanupTaskReports()
- getSetupTaskReports()
- getTaskCompletionEvents()
- getTaskDiagnostics()
- setJobPriority()
> Refactor JobTracker.submitJob to not lock the JobTracker during the HDFS
> accesses
> ---------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1354
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1354
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Reporter: Devaraj Das
> Assignee: Arun C Murthy
> Priority: Critical
> Attachments: MAPREDUCE-1354_yhadoop20.patch
>
>
> It'd be nice to have the JobTracker object not be locked while accessing the
> HDFS for reading the jobconf file and while writing the jobinfo file in the
> submitJob method. We should see if we can avoid taking the lock altogether.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
