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 "zhihai xu (JIRA)" <ji...@apache.org> on 2014/08/01 00:39:38 UTC

[jira] [Created] (MAPREDUCE-6020) Too many threads blocking on the global JobTracker lock from getJobCounters, optimize getJobCounters to release global JobTracker lock before access the per job counter in JobInProgress

zhihai xu created MAPREDUCE-6020:
------------------------------------

             Summary: Too many threads blocking on the global JobTracker lock from getJobCounters, optimize getJobCounters to release global JobTracker lock before access the per job counter in JobInProgress
                 Key: MAPREDUCE-6020
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6020
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
    Affects Versions: 0.23.10
            Reporter: zhihai xu
            Assignee: zhihai xu


Too many threads blocking on the global JobTracker lock from getJobCounters, optimize getJobCounters to release global JobTracker lock before access the per job counter in JobInProgress. It may be a lot of JobClients to call getJobCounters in JobTracker at the same time, Current code will lock the JobTracker to block all the threads to get counter from JobInProgress. It is better to unlock the JobTracker when get counter from JobInProgress(job.getCounters(counters)). So all the theads can run parallel when access its own job counter.



--
This message was sent by Atlassian JIRA
(v6.2#6252)