[
https://issues.apache.org/jira/browse/MAPREDUCE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869333#action_12869333
]
Dmytro Molkov commented on MAPREDUCE-1354:
------------------------------------------
Is there any particular reason that only getTaskCompletionEvents dropped the
synchronized modifier, but all other job access methods like
getCleanupTaskReports, getSetupTaskReports, etc are still syncrhonized, while
effectively they are doing a very similar kind of access?
> Incremental enhancements to the JobTracker for better scalability
> -----------------------------------------------------------------
>
> 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: Dick King
> Priority: Critical
> Attachments: mapreduce-1354--2010-03-10.patch,
> mapreduce-1354--2010-05-13.patch, MAPREDUCE-1354_yhadoop20.patch,
> MAPREDUCE-1354_yhadoop20.patch, MAPREDUCE-1354_yhadoop20.patch,
> MAPREDUCE-1354_yhadoop20.patch, MAPREDUCE-1354_yhadoop20.patch,
> MAPREDUCE-1354_yhadoop20.patch, MAPREDUCE-1354_yhadoop20.patch,
> mr-1354-y20.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.
