[
https://issues.apache.org/jira/browse/MAPREDUCE-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-1354:
-------------------------------------
Environment: (was: Incremental enhancements to the JobTracker include
a no-lock version of JT.getTaskCompletion events, no lock on the JT while doing
i/o during job-submission and several fixes to cut down configuration parsing
during heartbeat-handling.)
Release Note: Incremental enhancements to the JobTracker include a no-lock
version of JT.getTaskCompletion events, no lock on the JT while doing i/o
during job-submission and several fixes to cut down configuration parsing
during heartbeat-handling.
> 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: Arun C Murthy
> Priority: Critical
> Attachments: 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
>
>
> 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.
