You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Scott Chen (JIRA)" <ji...@apache.org> on 2010/08/05 04:00:17 UTC
[jira] Resolved: (MAPREDUCE-1995) FairScheduler can wait for
JobInProgress lock while holding JobTracker lock
[ https://issues.apache.org/jira/browse/MAPREDUCE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Chen resolved MAPREDUCE-1995.
-----------------------------------
Resolution: Invalid
After looking at it more carefully, I think this may not be a problem.
Because when FairScheduler calls updateLastMapLocalityLevel(), the JobInProgress is already initialized.
JobInProgess.initTasks() is what make things slow.
Sorry for the spam.
> FairScheduler can wait for JobInProgress lock while holding JobTracker lock
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-1995
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1995
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/fair-share
> Affects Versions: 0.21.0
> Reporter: Scott Chen
> Assignee: Scott Chen
> Fix For: 0.22.0
>
>
> Here is the related code path.
> {code}
> JobInProgress.getTaskInProgress() (Locks JobInProgress)
> LocalityLevel.fromTask()
> FairScheduler.updateLastMapLocalityLevel()
> FairScheduler.assignTasks()
> JobTracker.heartbeat() (Locks JobTracker)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.