[
https://issues.apache.org/jira/browse/MAPREDUCE-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081827#comment-14081827
]
Hadoop QA commented on MAPREDUCE-6020:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12659032/MAPREDUCE-6020.branch1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4781//console
This message is automatically generated.
> 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
> Attachments: MAPREDUCE-6020.branch1.patch
>
>
> 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)
